export_pdf

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

Annotations only provide readOnlyHint=true; description adds return value structure (nodeId, path, empty?), edge cases (path null if missing/not exportable, empty:true for blank PDF), and rendering behavior (one page per node, no pagination). No contradiction with annotations.

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?

Three concise sentences: purpose, limitations, guidance/return info. Front-loaded with main action. No unnecessary 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?

Given no output schema, description fully explains return shape and edge cases. Covers parameter behavior, limitations, and alternative sibling. Complete for a simple export tool.

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 with descriptions. Description adds value by explaining that omitting nodeId exports current page, which is not in schema. Does not repeat schema details, effectively supplementing it.

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?

Specifically states verb (export), resource (node/page), and output (vector PDF). Distinguishes from sibling save_screenshots by specifying vector vs raster. Clarifies limitations (single-page, cannot paginate).

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?

Explicitly tells when to use (vector PDF) and when not (use save_screenshots for raster). Provides guidance on nodeId omission for current page and warns about slow performance for large pages.

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