Download a report PDF (binary body)

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description earns credit for the one genuinely useful addition: the response is a binary body (not JSON), which affects how the agent must handle the result. It omits error behavior for missing/not-yet-generated reports, leaving a 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?

It is one short sentence with the resource type front-loaded and no filler, but it is minimal to the point of being a restated title; the parenthetical endpoint adds only slight value. There is no waste but also little substance.

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 single-parameter download tool with no output schema, the description covers the essential fact that the response is binary. It still omits what an agent needs for correct invocation: where the id comes from, failure modes when the PDF is not yet available, and how this differs from the HTML/public render variants.

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?

There is a single required 'id' parameter with 0% schema description coverage. The embedded path '/v1/reports/{id}/pdf' implies the id is a report identifier used as a path segment, which is a small but real clarification. Beyond that, it says nothing about the id's format or source (e.g. from reports_list/reports_get).

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 concrete verb+resource ('Download a report PDF') and the underlying endpoint path, so the basic action is clear. However, it does nothing to distinguish this from nearby siblings such as reports_renderHtml, reports_get, or publicReports_pdf, which an agent must choose between. It is essentially the title plus a path.

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?

There is no guidance on when to use this instead of reports_get (metadata), reports_renderHtml (inline HTML), or publicReports_pdf (public variant), nor any prerequisite such as whether the report must be generated first. The agent must infer the selection rule from the tool names alone.

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