export_pdf

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

Annotations only state destructiveHint=false; the description adds that it uses Inkscape and produces a 'validated PDF' via 'bounded, allowlisted options,' which hints at security constraints. However, it does not disclose side effects such as whether the output file is created at outputPath, how expectedRevision is used for concurrency, or what happens on validation failure. Given sparse annotations, this is a moderate gap.

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, efficient sentence with no wasted words. It front-loads the core action ('Exports an SVG document to a validated PDF') and adds a constraint ('bounded, allowlisted options'). It is appropriately concise, though it sacrifices necessary detail.

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?

For a tool with six parameters, four required, and no schema descriptions, the description is severely incomplete. It does not explain the role of expectedRevision, the workspace-scoped identifiers, the output path semantics, or the validation process. The existence of an output schema does not compensate for the missing parameter guidance. An agent cannot correctly call this tool with the given information.

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 has zero descriptions for all six parameters, and the description does not mention any of them. There is no explanation of what path, outputPath, workspaceId, expectedRevision, pdfVersion, or expectedOutputRevision mean. The phrase 'bounded, allowlisted options' is too vague to clarify parameter semantics. With 0% schema coverage, this is a critical failure.

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 the tool exports an SVG document to a validated PDF via Inkscape, with a specific resource and target format. It distinguishes from sibling tools like export_png and export_svg by format, so an agent can tell them apart without opening schemas.

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 implied by the name and format (PDF vs PNG/SVG), but no explicit guidance is given on when to use this tool versus alternatives. There is no mention of when not to use it, no exclusions, and no context like workspace prerequisites. The description offers only implicit direction.

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