Skip to content

Conversation

@triepod-ai
Copy link

Summary

  • Add readOnlyHint and destructiveHint annotations to all 80 tools across 9 tool modules
  • These annotations help LLMs understand tool behavior and make better decisions about tool usage
  • All 665 tests pass with updated test infrastructure

Tool Annotation Summary

File Read-Only Destructive Total
core.ts 3 0 3
pipelines.ts 9 3 12
repositories.ts 11 7 18
work-items.ts 11 9 20
wiki.ts 5 1 6
test-plans.ts 4 5 9
search.ts 3 0 3
advanced-security.ts 2 0 2
work.ts 4 3 7
Total 52 28 80

Changes

  • Added title, readOnlyHint, or destructiveHint annotations to each server.tool() call
  • Updated tests to account for new annotation parameter position
  • No functional changes to tool implementations

Test plan

  • All 665 existing tests pass
  • Build succeeds without errors
  • Annotations verified in compiled output

🤖 Generated with Claude Code

Add readOnlyHint and destructiveHint annotations to all 80 tools across
9 tool modules to help LLMs understand tool behavior:

- core.ts: 3 read-only tools
- pipelines.ts: 9 read-only, 3 destructive
- repositories.ts: 11 read-only, 7 destructive
- work-items.ts: 11 read-only, 9 destructive
- wiki.ts: 5 read-only, 1 destructive
- test-plans.ts: 4 read-only, 5 destructive
- search.ts: 3 read-only
- advanced-security.ts: 2 read-only
- work.ts: 4 read-only, 3 destructive

Updates tests to accommodate new annotation parameter position in
server.tool() calls.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@triepod-ai triepod-ai requested a review from a team as a code owner December 27, 2025 13:38
@triepod-ai
Copy link
Author

@microsoft-github-policy-service agree

@danhellem
Copy link
Contributor

As noted clearly in the contributions.md file, you need to create an issue first and articulate the need. Then we will review before accepting any related PR's. Closing this PR.

@danhellem danhellem closed this Dec 29, 2025
@danhellem danhellem added the Do Not Merge ❌ do not merge this pull request label Dec 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Do Not Merge ❌ do not merge this pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants