understand_technical_diagram

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

With no annotations, the description carries the full burden. It discloses the tool's specialty and scope but doesn't mention output format, limitations, or any requirements beyond image input. For an analysis tool, this is adequate but not rich; no contradictions with annotations (none present).

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 four sentences, each serving a purpose: defining the tool, giving usage directives, stating its specialization, and listing exclusions. There is no fluff or redundancy; every sentence earns its place.

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?

Despite lacking an output schema and annotations, the description provides a complete picture of the tool's purpose, scope, and usage boundaries. The main gap is the unspecified return format, but 'explain' implies a text response, so the completeness is high.

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 100%, meaning each parameter (image_source, prompt, diagram_type) has its own description. The tool description adds no additional parameter-level semantics beyond what the schema already provides, so a baseline 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 tool's verb+resource: 'Analyze and explain technical diagrams' and enumerates specific types (architecture, flowcharts, UML, ER, system design). It distinctly separates this from siblings by providing explicit exclusions, making the purpose 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 gives explicit when-to-use ('Use this tool ONLY when...') and when-not-to-use ('Do NOT use for: UI screenshots...') but does not name specific alternative tools. Despite this, it offers clear usage boundaries and context, which is nearly a 5 except for the missing explicit alternatives.

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