Export a diagram

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

Annotations indicate readOnlyHint=true, which aligns with the read-only export operation. The description adds meaningful context beyond the annotation: it notes that SVG export is a paid feature and that the return value is the file content directly, which is not obvious from the schema.

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?

Three sentences, no filler, and the key information is front-loaded. Every sentence adds value: formats, output nature, and a caveat.

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 two-parameter tool with a solid annotation and complete schema coverage, the description fully covers behavior, output format, and an important exception. No missing information is evident.

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 coverage is 100%, providing basic descriptions for both parameters. The description enriches the 'format' parameter by explaining that 'drawio' opens at app.diagrams.net and that SVG is paid, which is valuable guidance not present in the schema.

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 a specific verb ('Export') and resource ('diagram'), clarifies the output formats ('drawio' or 'svg'), and states that it returns file content directly. This clearly distinguishes it from sibling tools like get_diagram or list_diagrams.

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 implies when to use it (when you need the raw file content) and mentions the available formats. It doesn't explicitly name alternatives or exclusion criteria, but the context is clear enough for an agent to select it over other diagram tools.

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