export_pdf

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 only states the action and target path but does not disclose whether existing files are overwritten, whether directories must exist, or any error behavior. This is a significant gap for a file-writing operation.

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 a single, front-loaded sentence of nine words. Every word contributes to the core meaning, and there is no redundancy or filler.

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 tool is simple (one parameter, no output schema), the description is minimally viable. However, it lacks details about file overwriting, path validation, or how it integrates with the drawing lifecycle. The presence of an output schema covers return values, but behavioral context is still thin.

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 schema provides only a string 'path' with no description (0% coverage). The description adds 'at path' but does not clarify whether it expects a file path or directory, whether the .pdf extension is appended, or any formatting requirements. The description offers only minimal compensation for the missing schema detail.

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 'Export the drawing to PDF at path' with a specific verb and resource. It also adds 'the final deliverable' to indicate the tool's role, and the PDF format distinguishes it from sibling export tools like export_dxf and save_as_dwg.

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 implies use when a PDF export is needed, but it does not explicitly mention alternatives or when not to use it. The phrase 'final deliverable' hints at a purpose, but there is no direct comparison to sibling tools or exclusions.

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