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

Annotations only cover the safety profile (readOnly, not open-world), and the description adds genuinely new behavioral detail: three delivery channels (base64 pdf_base64, embedded PDF resource, and a /reports/<report_id>.pdf URL) plus an explicit auth requirement ('Requires the organization API key'). With no output schema, this return-format disclosure carries real weight.

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 tight sentences: identity/audience front-loaded, then the return mechanics and auth prerequisite. Nothing is redundant and there is no filler.

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 read tool with no output schema, the description covers what is returned and what credentials are needed, which is most of what an agent needs. It stops short of describing error conditions (e.g., unsealed or missing report) or whether the org key is passed as a header vs. query parameter.

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 100% and the single parameter already documents that report_id comes from ledger_compliance_report, so the description adds no new parameter meaning beyond what structured data provides. Baseline 3 applies.

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 names a concrete artifact (a finished PDF of a sealed compliance report) and its audience, so an agent knows exactly what comes back. It does not, however, contrast itself with ledger_compliance_report (which produces the report) or ledger_verify_report, leaving sibling differentiation to inference.

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: the report is 'for auditors and customers' and report_id comes from ledger_compliance_report, which hints at the sequencing. There is no explicit statement of when to call this instead of ledger_compliance_report, nor any failure/'report not sealed yet' guidance.

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