export_file

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

No annotations are provided, so the description carries the burden, and it does substantial work by disclosing a non-obvious failure mode: Inkscape exits 0 on an empty export, so this tool verifies the output exists and is non-empty. It does not explicitly restate the overwrite behavior of output_path, but that is already documented in the schema, and the verification detail adds real value beyond the structured fields.

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 two dense sentences with no filler: the first front-loads the formats and key controls, the second adds the critical verification behavior. Every sentence earns its place.

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?

The description covers the headline formats and a key failure mode, which is useful for a tool with 19 optional parameters. However, it leaves important context implicit: how the export format is selected (presumably by output_path extension) and what the default export scope is when no area/id/margin options are provided. With no output schema and no annotations, a bit more orientation would make this fully complete.

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 100%, so the baseline is 3. The description groups parameters into meaningful categories (dpi, size, margin, area, background, text-to-path, compression) which aids orientation, but it does not add semantic details beyond what the schema already provides.

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 names the action ('Export') and the target resource formats ('PNG, SVG, PDF, PS or EPS'), and it gives a concrete sense of the tool's capability with 'full control' and its option list. It does not explicitly differentiate from sibling tools like export_batch or export_preview, so the distinction is implied rather than stated.

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?

There is no explicit guidance on when to use this tool versus export_batch or export_preview, nor any exclusion criteria. The phrase 'with full control' hints that this is the more configurable single-file export path, but the agent is left to infer the routing decision.

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