export_pdf

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

With no annotations, the description carries the full burden. It usefully discloses that backgrounds, ink, and images are all included, but says nothing about whether a file is written/overwritten, where it lands, permission or licensing requirements, or how scale affects fidelity.

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?

One sentence, front-loaded with the verb and resource, no filler. The parenthetical earns its place by enumerating rendered layers.

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?

An output schema exists, so return values need not be explained, but with zero annotation coverage and three undocumented parameters the definition is not sufficient to call it confidently — the path/out relationship and scale meaning are unresolved.

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 coverage is 0% and the description mentions no parameters at all, leaving 'path' (required), 'out' (optional, and confusingly overlapping with path), and 'scale' (default 1.5) entirely unexplained. The description adds nothing beyond the raw schema titles.

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?

Specific verb+resource ('Render the whole notebook ... into a PDF') with a parenthetical enumerating what is rendered. The word 'whole' implicitly distinguishes it from page-level siblings like render_page and render_region, though it never names them.

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?

Usage is only implied through the scope word 'whole notebook'; an agent can infer this is the export-everything option rather than a single page. There is no explicit when-to-use statement, no exclusion, and no sibling is named despite render_page/render_region/design_mockup being nearby alternatives.

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