add_line

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

No annotations provided; description mentions it draws a line and returns a success message but does not disclose potential side effects, permissions, or whether the line is permanent. Adequate but not rich.

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?

Very concise with clear structure: purpose, usage, arguments, returns. Only 6 lines, front-loaded with key information.

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 purpose, usage, all 5 parameters, return type, and alternative tool. Complete for a simple drawing tool with 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?

Description explains each parameter in the Args section, including that coordinates are in data coordinates, adding meaning beyond schema titles (0% schema description coverage).

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?

Description states 'Draw a straight line between two data points on a graph' with specific verb+resource and distinguishes from sibling add_arrow.

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?

Explicitly says 'Useful for guides, connectors, and trend indicators' and provides alternative tool: 'For a line with an arrowhead, use add_arrow instead.'

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