Export PDF

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

No annotations (readOnlyHint, destructiveHint) provided, so description should disclose side effects. It only states export without mentioning whether the original file is modified, required permissions, or file overwrite behavior. Minimal transparency beyond the action.

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 short sentences: one for purpose, one for parameter details. No redundant words, front-loaded with primary action.

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?

Output schema exists, so return values are documented. Description covers main functionality and param semantics. Lacks mention of file overwrite behavior, error conditions, or prerequisites. Adequate for a simple export tool but missing some edge-case context.

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 covers 100% of parameters, so baseline 3. Description adds extra context for layout parameter: explains COM vs ezdxf rendering differences. This adds value beyond schema properties. However, path parameter gets only a brief description.

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?

Description clearly states 'Export the current drawing (or a paper-space layout) to PDF.' It specifies the verb (export), resource (drawing/layout), and format (PDF), distinguishing it from sibling export_dxf.

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?

Implicitly indicates use for PDF export, but lacks explicit exclusion or alternatives. Mentions layout parameter but no guidance on when to use model vs paper space. Sibling tools provide context but no direct comparison in description.

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