document_import_pdf

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

Annotations only declare destructiveHint=false, and the description adds substantial behavior beyond that: it discloses the produced artifacts (sanitized SVG plus a conversion manifest), that exactly one page is processed, and that non-default importers are capability-gated modes carrying fidelity warnings. It does not cover failure handling or the revision-safety behavior, but this is meaningful added context given the thin annotation set.

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, front-loaded sentences that lead with the core action and outcome, then add the mode caveat. No filler, though the second sentence is jargon-heavy and could read as an afterthought rather than actionable guidance.

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 no explanation, and the description establishes the general workflow (import one page to sanitized SVG + manifest). However, for a 10-parameter tool with nested objects it omits why expectedRevision is required, what the dependencyPolicy does, and how mode capability-gating affects the call, so an agent still lacks enough to invoke it confidently.

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 description coverage is 0%, so the description carries the full burden, yet it only indirectly gestures at mode, page, sanitize/output, and manifestPath. It never explains fontStrategy (six enum values), the nested dependencyPolicy, or the required expectedRevision hash, leaving required parameters undocumented in both schema and prose.

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 verb (Imports) and resource (exactly one page of a workspace-local PDF) with a clear output (sanitized SVG and conversion manifest), which separates it from the SVG/raster/PostScript/EMF import siblings. It stops short of distinguishing itself from the generic document_import, but the PDF specificity and one-page scope are precise.

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 names the three importers (Inkscape/internal/Poppler) but never says when to pick this tool over document_import, document_import_svg, or the other import siblings, nor when to choose internal vs Poppler. 'Capability-gated' hints that document_import_capabilities should be consulted first, but no alternative or condition is stated explicitly.

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