generate_diagram

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

No annotations provided; description only says 'generate' with no details on side effects, limitations, or behavior. Lacks disclosure of any important behavioral traits beyond the basic action.

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?

Description is very short (7 words) but not structured. While concise, it could add more value without becoming verbose. Minimalism here sacrifices clarity.

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?

Tool has 8 parameters, no output schema, no annotations. Description is insufficient to fully guide an agent; lacks information on return values, error cases, or behavioral nuances.

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 has 100% description coverage for all 8 parameters. Description adds no additional meaning beyond stating the tool's purpose; it does not explain parameter contexts or enhance understanding.

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?

Description clearly states action 'generate' and resource types (technical diagrams, flowcharts, architectural mockups). Differentiates from siblings like generate_image (general images) and generate_icon (icons).

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 explicit guidance on when to use vs alternatives. The enum for 'type' implies intended diagram types, but no when-not-to-use or sibling comparisons are provided.

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