Export Drawing

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds meaningful behavior beyond that: headless execution, the different composition paths for PDF/SVG versus DXF, and the exact return object fields. It does not explicitly mention overwrite semantics, but with annotations covering the destructive nature, the added transparency is strong.

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?

Two dense sentences with no filler. The first sentence front-loads the core operation, format options, and headless behavior; the second explains the two rendering pathways and the return value. 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?

For a two-parameter synchronous export tool with no output schema, the description is quite complete: it covers format inference, composition behavior, and the return shape. It could add explicit warnings about file overwrites or page identification details, but given the annotations and the compact scope, nothing critical is missing for an agent to call it correctly.

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?

With 0% schema description coverage, the description must carry parameter meaning, and it partially does: 'page' is the drawing page to export and 'path' is the target whose extension selects the format. However, 'page' remains vague as an identifier/name, and path details such as overwrite behavior or path requirements are unspecified. It compensates for the schema silence but not fully.

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 operation ('Export a drawing page') and enumerates the target formats PDF, SVG, or DXF, with format inferred from the path extension. This clearly distinguishes it from shape-focused siblings like export_shape and sheet-focused siblings like sheet_flat_export. The verb+resource+scope are all present and unambiguous.

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 makes it clear this is for exporting a drawing page headlessly, with format selection driven by the file extension. It does not explicitly name alternative tools or exclusion conditions, but the context is strong enough for an agent to recognize when this tool applies versus other export/render tools.

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