Export a run as PDF

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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuinely new behavioral context: the URL expires after 1 hour and there is a base64 fallback when storage is unavailable. It stops short of stating permission or auth requirements, so it is strong but not exhaustive.

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?

A single, tightly packed sentence that front-loads the operation and then the output detail; no filler, no redundancy, every clause earns its place.

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?

There is no output schema, yet the description adequately explains the return value (signed URL, expiry, base64 fallback) and the render format. For a one-parameter tool the only real gap is guidance on run_id and any run-state preconditions, which is minor.

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% and the sole parameter run_id has no schema description, so the description is the only place semantics could be added. It says nothing about run_id (format, source, or how to obtain it), leaving the name alone to carry meaning; acceptable but not compensating for the coverage gap.

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 states a precise verb+resource ('render a run's results as a theme-sectioned PDF') and names the return artifact (signed download URL). This is unmistakably distinct from every sibling such as get_run_results or list_playbooks, so an agent can select it without ambiguity.

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: exporting a run's results as the 'validated deliverable format' suggests a post-run deliverable step, but there is no explicit statement of when to call this versus, say, get_run_results or get_run_status. No exclusions or preconditions (e.g., run must be complete) are given.

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