understand_technical_diagram

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

With no annotations, the description is the sole source of behavioral information. It only states that the tool interprets technical diagrams and accepts an optional question, but does not disclose processing details, limitations, or output characteristics beyond what the output schema would imply.

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 short, front-loaded with the main purpose, and the Args section is compact and free of filler. Every sentence contributes useful 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?

For a relatively simple two-parameter tool with an output schema, the description adequately covers input formats and the tool's scope. It does not explicitly differentiate from sibling tools, but the diagram-type examples provide enough contextual guidance for selection and invocation.

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?

The schema only defines 'image' and 'question' as strings with zero description coverage, so the description's Args section adds essential meaning. It specifies that image can be a path, URL, or base64 URI, and explains that question is optional and targets specific aspects of interest.

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 uses the specific verb '解读' (interpret) and clearly identifies the resource as technical diagrams, listing concrete types such as architecture, flowchart, UML, ER, and system design. This clearly distinguishes it from generic sibling tools like image_analysis.

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 clear context by enumerating the types of diagrams this tool is meant for, which tells an agent when to use it. However, it does not explicitly mention alternative tools or state when not to use it, so it lacks direct exclusions.

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