export_excalidraw

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

The description adds one behavioral detail: it uses a headless browser for rendering identical to excalidraw.com. However, with no annotations provided, the description carries the full burden. It does not disclose side effects (e.g., file creation, overwriting behavior), performance implications, or required permissions. The rendered output fidelity is a positive but incomplete disclosure.

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 highly concise, consisting of two sentences that are front-loaded with the core purpose. Every sentence adds value—the first states the action and formats, the second clarifies the rendering method. There is no redundant or filler 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?

Given the complexity of 6 parameters (1 required) and no output schema, the description covers the primary action but lacks details on output file behavior (e.g., where files are saved, naming conventions, return values). It mentions rendering quality but not the process of file creation or error handling. The description is adequate for a simple tool but incomplete for a tool with multiple parameters and no output schema.

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% (all parameters have descriptions in the schema), so the baseline is 3. The description does not add any additional meaning beyond the schema—it does not explain parameter usage, constraints, or relationships. The schema itself provides adequate documentation, but the description contributes nothing extra.

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 clearly states the tool exports an Excalidraw diagram to PNG or SVG format, with the added detail of using a headless browser for pixel-perfect rendering. The verb 'Export' and resource 'Excalidraw diagram' are specific, and the mention of formats distinguishes it from sibling tools like export_excalidraw_batch (batch export) and get_excalidraw_info (info retrieval).

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 provides no guidance on when to use this tool versus its siblings (export_excalidraw_batch for batch, get_excalidraw_info for information). There is no mention of prerequisites, context for use, or alternatives. The tool's purpose is implied but not contrasted with similar tools.

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