get_diagram_info

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'get basic information', which implies a read operation, but it does not disclose what 'basic information' consists of, whether permissions are needed, or what the response format is. No output schema exists, so the description should provide more context.

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 a single, short phrase that efficiently communicates the core purpose without unnecessary words. It is appropriately sized for a simple tool, though it could have been more informative without becoming verbose.

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 simple tool with one parameter, the description is still insufficient. It does not explain what 'basic information' includes, does not describe the return value, and does not differentiate from similar tools like load_diagram or get_statistics. This leaves the agent without enough context to decide when to use it or what to expect.

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% (diagram_id is documented as '图表ID' meaning diagram ID), so the baseline is 3. The description does not add any additional meaning to the parameter beyond the schema, such as expected format or examples, but it is not misleading.

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 '获取图表基本信息' (get diagram basic information) states a clear verb+resource action, indicating it retrieves basic information about a diagram. However, it does not specify what 'basic information' includes or distinguish it from sibling tools like load_diagram or get_statistics, so it's not fully differentiated.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. For example, it is unclear whether this should be used to fetch metadata vs. full content, or how it relates to load_diagram.

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