add_arrow

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

No annotations provided, so the description carries full burden. It explains arrowhead placement (at (x2,y2) and start if double_headed), double_headed option, and head_size default (10). This is sufficient for basic behavioral understanding.

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?

Well-structured with a clear initial sentence. The Args section is slightly lengthy but necessary given no schema descriptions. Could be condensed, but no redundancy.

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?

Covers all essential information: what the tool does, parameters with explanations, and return type (success message). Given no annotations, this is adequate for a tool with 7 parameters and an output schema.

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 has 0% description coverage (only titles/types), so the description must add meaning. It provides detailed explanations for all parameters: graph_name, x1,y1 (tail), x2,y2 (head), double_headed option, head_size default.

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 'Draw an arrow from (x1,y1) to (x2,y2) at data coordinates', specifying the verb (draw), resource (arrow), and coordinates. It differentiates from siblings like add_line (line without arrow) and add_text_annotation (text).

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?

No explicit guidance on when to use this tool vs alternatives. The description implies use for directional annotations, but does not mention cases where add_line or other annotation tools might be more appropriate.

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