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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description adds value by declaring the auth scope (`passes:download`), the exact GET endpoint, and billing/rate-limit parity. The guardrail 'Do not invent other paths' adds a useful constraint beyond the structured fields. No contradiction with the read-only annotations.

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?

Every line earns its place: the one-line purpose summary, the wallet disambiguation, the scope, the OpenAPI mapping, and the billing/rate-limit guardrail. It is compact, logically grouped, and front-loaded with the core action.

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?

With all three parameters fully documented in the schema and annotations carrying the safety profile, the description covers the return format (the .pkpass binary) and the active-pass constraint. It doesn't describe error behavior for unknown or inactive serials, which is a minor gap for a no-output-schema tool.

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 the baseline is 3; the description restates the wallet_type disambiguation that the schema already documents in detail. No additional semantics are added for serial_number or x_app_id beyond what the schema provides.

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 opening line 'Download a .pkpass file by serial number' names a specific verb, resource, and lookup key, and the description adds that it applies to an 'active pass.' This differentiates it from siblings like downloadPass (presumably by pass ID) and getPassBySerial (metadata, not the binary).

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?

The description gives clear context for the wallet_type parameter — use it when a serial has both Apple and Google passes, defaulting to apple — but never names sibling tools or states when to choose this over getPassBySerial or downloadPass. Usage relative to alternatives is only implied by the phrase 'Download the .pkpass binary.'

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