Set Annotations

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

Annotations already provide idempotentHint and openWorldHint. The description adds the batched nature and conditional update behavior, which adds context but does not reveal additional side effects or constraints beyond what annotations hint at. The description does not contradict annotations.

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 a single, well-structured sentence that conveys the purpose and key behavior efficiently. Every part is necessary; no wasted words. It is front-loaded with the primary action.

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 tool has a rich input schema (100% coverage) and an output schema exists, the description covers the core logic (batched upsert). It does not mention error handling or limits, but for a batched data tool this is sufficient. Slightly more detail on expected usage patterns would push to 5.

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 each parameter. The description adds meaning beyond the schema by explaining the conditional logic involving annotationId (create vs update). This helps the agent understand parameter interplay without repeating schema details.

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 tool's action: 'Create or update native annotations on one or more nodes in a batched call'. It specifies the per-item logic (annotationId present = update, absent = create), distinguishing it from sibling tools like annotation_list (which lists annotations only).

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 explicitly mentions batched operation and the logic for create vs update, giving clear context. However, it does not explicitly state when not to use this tool or mention alternatives beyond the implied reading tool (annotation_list). It could be slightly improved with exclusionary guidance.

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