技术图理解

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

No annotations are provided, so the description carries full burden. It does not explicitly state that the tool is read-only or disclose any behavioral traits (e.g., no mention of modifications, output format). The nature suggests analysis, but more detail would improve transparency.

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 concise: one sentence in Chinese with a front-loaded list of diagram types and a use-case sentence. It efficiently conveys purpose and usage, though could be slightly more structured.

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 has 5 parameters (1 required) and an output schema, the description covers the key aspects: diagram types, focus areas, and usage context. It does not detail output format, but output schema exists. Fairly complete for a straightforward interpretation tool.

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% with well-described parameters. The description adds value for overall purpose but does not elaborate on specific parameters beyond what the schema provides. Baseline of 3 is appropriate as schema does the heavy lifting.

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 explicitly states the tool interprets technical diagrams (architecture, flow, UML, ER, sequence) focusing on nodes, connections, processes, and design intent. It also provides a clear usage context: 'use when you need to read a technical schematic diagram'. This differentiates it from general image analysis tools.

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 includes '当需要读懂一张技术示意图时使用' (use when you need to read a technical schematic diagram), providing clear when-to-use guidance. However, it does not explicitly state when not to use or mention alternative sibling tools, though the context of sibling names implies differentiation.

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