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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful scope detail by enumerating the content the response will contain (fields, paper styles, privacy model), but does not describe the response shape or whether the answer is static documentation versus a live data query.

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 sentence that front-loads the core purpose and then lists the covered topics. No filler, no restatement of the title beyond what is needed to convey scope.

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 zero-parameter, read-only reference tool with full annotation coverage, the description gives enough to know what knowledge it returns. The only remaining gap is that no output schema exists and the description doesn't indicate how the explanation is structured or whether it's static text.

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 tool takes no parameters, so there is nothing for the description to disambiguate; baseline for zero-param tools applies. The description correctly implies no input is needed to retrieve this reference material.

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?

States a specific verb ('Explain') plus the exact subject matter: what Ship Receipt is, its fields, paper styles, and privacy model. It is clearly distinguishable from the sibling generate_receipt (this informs, that produces), though it doesn't explicitly name the sibling to reinforce the contrast.

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 rather than stated: an agent can infer this is the reference lookup to call before or instead of generate_receipt, but there is no explicit 'use this when...' instruction or exclusion. Adequate for a zero-parameter informational tool, but the routing guidance is left to inference.

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

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds genuinely new behavior: the image is returned inline, the figures are user-supplied and the receipt labels them as such, and nothing is stored or transmitted. That privacy and data-provenance disclosure is exactly the kind of context annotations cannot convey; only the verdict-derivation rules are left implicit.

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?

Four compact sentences, front-loaded with the output format and pixel dimensions, then behavior, then the privacy caveat. Each sentence carries information; the only redundancy is restating the metric list already present in the schema.

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 an 11-parameter, closed-world render tool with an output schema and full annotation coverage, the description supplies the missing narrative: what gets rendered, the verdict taxonomy, and the no-storage guarantee. Minor styling parameters are left entirely to the schema, which is acceptable given full description coverage there.

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 100%, so every parameter is already documented, and the description only echoes the four headline metrics while explaining the verdict tiers they feed into. It adds a little semantic value about how inputs become output but nothing on theme, lang, currency, note, or example beyond the 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?

The description states a concrete verb and artifact ('Print a 1200x675 launch receipt PNG') and even enumerates the metrics printed (visits, signups, revenue, cost) plus the verdict outcomes. It is unmistakable what the tool produces, but it never mentions the sibling describe_ship_receipt, so an agent gets no explicit differentiation between the two.

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 context is only implied by 'so the user can save it or post it on X', which suggests a user-facing artifact rather than a programmatic API call. There is no statement of when to prefer this over describe_ship_receipt, no prerequisites, and no exclusions.

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