create_diagram

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

No annotations are provided, so the description carries the full burden. '创建通用图表' discloses no side effects, return behavior, permissions, or validation details. For a write operation, this is completely inadequate.

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, which is extremely concise but under-specified. It is not 'appropriately sized' because it lacks necessary context. This is under-specification, not efficient conciseness.

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?

With 4 parameters, a rich enum, no output schema, and many sibling tools, the description provides almost no context. It fails to explain what 'general' means, how this relates to specialized creators, or what the tool returns. Entirely insufficient.

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%, so the baseline is 3. The description adds no extra meaning about how the parameters relate or should be used, but it does not mislead either.

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 states the tool creates general diagrams, which is a clear verb+resource, but 'general' is vague and does not differentiate it from specialized creation siblings like create_flowchart or create_org_chart. The schema enum lists supported types, but the description itself lacks that specificity.

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?

There is no guidance on when to use this tool versus alternatives. With multiple sibling tools for specific diagram types (create_flowchart, create_org_chart, create_mindmap), the description offers no criteria for choosing the generic create_diagram.

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