export

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

No annotations are provided, so the description carries the full burden. It usefully discloses that the output format is derived from the file extension (.svg, .png, .pdf, etc.), which is real behavioral info, but says nothing about overwrite behavior, permissions, errors, or where the file lands.

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?

A single front-loaded sentence with the format mapping immediately following; no wasted words.

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?

Reasonable for a 3-param tool with no output schema and no annotations, since the schema covers page/path semantics and the description covers output format. However, without an output schema the description should hint at what is returned (e.g., file path) and state the state-mutation implications of the live-board path.

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?

The `output` parameter has no schema description, and the description compensates well by enumerating the accepted extensions and explaining the format-selection logic. `page` and `path` are covered by the schema, so the description fills the main gap.

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?

States a specific verb and resource ("Exports a page to a file") plus the key format dimension. It does not distinguish itself from siblings like render or save_board, so the reader must infer where this fits among export-like tools.

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 format-by-extension rule implies usage, but there is no explicit when-to-use vs alternatives (e.g., render, save_board, batch) nor any exclusions or prerequisites stated.

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