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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds value by disclosing the required OAuth scope (passes:read), the exact HTTP mapping, and billing/rate-limit consistency, which are useful behavioral/operational traits beyond the 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?

The description is brief and front-loaded with the core purpose, followed by scope/endpoint details and a guardrail against inventing paths. There is slight redundancy between 'Get a pass' and 'Returns the full details of a single pass,' but overall it is efficient and well-structured.

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 simple get-by-ID tool with strong annotations and fully documented schema, the description covers the core purpose, endpoint mapping, scope, and rate-limit consistency. It does not explain error cases or how to choose between getPass and getPassBySerial, but the context is largely sufficient for correct invocation.

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 both parameters (id and x_app_id) are already fully documented in the schema. The description does not add any parameter semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 specific verb and resource: 'Returns the full details of a single pass' and maps to GET /manage-passes/{id}. This clearly identifies the operation and, through the {id} path, implies it differs from the sibling getPassBySerial, though it does not name any sibling explicitly.

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 getPass versus alternatives like listPasses or getPassBySerial. The description provides constraints ('Same PassFast HTTP API, billing, and rate limits. Do not invent other paths.') but does not explain the selection criteria among sibling tools.

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