document_export_preset_plan

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

Consistent with readOnlyHint=true: 'without publishing files' confirms no side effects. Beyond annotations it discloses the owner-bound, single-use, expiring token and that the plan is pinned to the source revision and observed Inkscape capabilities. It omits what happens on expiry or token misuse, so not a 5.

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 sentences, front-loaded with the core action and output. Slight redundancy between 'single-use plan token' and 'must use the token before it expires', but every sentence is relevant.

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 covers the preflight-then-execute contract. Against a parameter count of 3 with a large nested preset object at 0% coverage, though, the description leaves several structural details to the schema alone.

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%, so the description carries the burden. It meaningfully hints at preset name, source revision (expectedRevision), and TTL ('before it expires'), but never mentions workspaceId or the preset's outputDirectory/metadata/overrides structure. Partial compensation for a deeply nested schema.

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?

Names a specific verb and resource ('Preflights one named export preset'), states the key output ('single-use plan token'), and clarifies it does not publish files, which separates it from the export siblings. It does not name an alternative (e.g., document_export) explicitly, so it stops short of 5.

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: preflight a preset, then execute with the returned token before expiry. However it never names the tool that consumes the token nor states when to prefer this over sibling exports like document_export or document_export_batch, leaving the agent to infer the workflow.

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