Manage annotation

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description mentions create and comment as write operations, and list/enclosed as reads, which aligns with annotations (readOnlyHint false, destructiveHint false). However, it adds no extra context beyond the actions themselves, such as side effects or permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences front-loaded with the four actions, followed by the purpose. It is concise and wastes no words, though it could be slightly more structured with bullet points for clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high schema coverage and lack of output schema, the description covers the main purpose and actions adequately. It could improve by clarifying parameter requirements per action mode, but the schema descriptions partially cover this.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 9 parameters. The description does not add additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the four actions (create annotated box, set comment, list annotations, list enclosed ops) with specific verbs and resource. It distinguishes itself from sibling tools like document_network by focusing on annotations and comments.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lists actions but does not provide explicit guidance on when to use this tool vs alternatives like document_network or create_component. No when-not-to-use or alternative tool mentions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.