export_diagram

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose the operation and that a path to the exported file is returned, plus the 'currently svg supported' caveat. However, it does not mention whether the original .excalidraw file is modified, where the SVG is written, or whether existing files are overwritten.

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 compact and well structured: a one-sentence purpose, a minimal Args list, and a Returns line. It is front-loaded and every sentence earns its place with no superfluous content.

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 two-parameter conversion tool with an output schema and a single supported format, the description is complete enough to call correctly. It states the input, the supported format, and the returned artifact, leaving only minor conventional unknowns.

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 0%, but the Args section compensates by explaining both parameters: file_path is the path to the .excalidraw file, and format is the export format with SVG currently supported. This adds real meaning beyond the bare schema properties, though it does not explicitly mention format optionality (the schema default already covers that).

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 opens with a specific verb and resource: 'Export an .excalidraw file to SVG format.' This clearly states what the tool does and distinguishes it from the many create/import/modify/read sibling tools, none of which export files.

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 conversion purpose is clear and the tool is the only export-related sibling, so an agent can infer when to use it. However, the description does not explicitly state when to use it vs. alternatives, nor does it mention exclusions or prerequisites.

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