feat: Add tool annotations for improved LLM tool understanding #263
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds MCP tool annotations (
readOnlyHint,destructiveHint) to all tools to help LLMs better understand tool behavior and make safer decisions about tool execution.Changes
readOnlyHint: truetoget_figma_datatool (fetches data without modifications)destructiveHint: truetodownload_figma_imagestool (writes files to local disk)titleannotations for human-readable display@modelcontextprotocol/sdkfrom^1.10.2to^1.25.1for annotation supportWhy This Matters
Tool annotations provide semantic metadata that helps LLMs understand tool behavior:
Testing
pnpm build)tools/listreturns annotations in responseget_figma_data→readOnlyHint: true(only fetches Figma data)download_figma_images→destructiveHint: true(writes files to disk)Before/After
Before (
tools/listresponse):{ "name": "get_figma_data", "description": "Get comprehensive Figma file data..." }After:
{ "name": "get_figma_data", "description": "Get comprehensive Figma file data...", "annotations": { "title": "Get Figma Data", "readOnlyHint": true } }🤖 Generated with Claude Code