Create Annotation Node

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

With no annotations, the description carries full burden. It discloses the creation behavior and the conditional behavior for sourceNodeId, but does not discuss potential side effects, permissions, or destructive nature. It partially covers behavior but lacks depth.

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 very concise with only two sentences, no unnecessary words, and front-loads the main purpose. However, it could be slightly more structured to improve readability.

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's complexity (4 parameters, no required ones, no output schema) and the absence of annotations, the description is insufficiently complete. It does not explain the role of most parameters or the return behavior, leaving agents with significant unknowns.

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 description coverage is 0%, so the description must add meaning for all 4 parameters. It only addresses sourceNodeId implicitly. Title, content, and role are not mentioned, and the role enum is left unexplained. The description does not compensate for the schema's lack of descriptions.

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 action ('Create') and resource ('annotation node'), and implicitly distinguishes from sibling tools like 'add_node_to_grid' or 'update_annotation_node' by focusing on creation. It is specific and unambiguous.

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 provides guidance on when to omit sourceNodeId, but does not explicitly state when to use this tool versus alternatives like 'add_node_to_grid' or 'update_annotation_node'. Usage context is implied rather than clearly delineated.

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