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

Annotations already cover read-only, idempotent, non-destructive safety. The description adds useful context: pagination, scope, endpoint mapping, and billing/rate-limit equivalence. It does not detail the response shape or rate-limit behavior, but it does not contradict 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 compact and front-loaded: the core action, pagination, scope, endpoint, and important constraints are each covered in a few sentences with no filler or redundancy.

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 read-only list operation with 10 optional but fully schema-described parameters, the description provides the missing context: current-app scoping, exact endpoint, and scope. It does not describe the return payload, but that is a modest gap given the simple listing purpose and absence of an output schema.

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%, with every parameter having its own description, so the description does not need to repeat parameter meanings. The 'paginated' mention aligns with limit/offset but adds no new semantics 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 clear verb and resource ('List passes') and specifies that it returns a paginated list for the current app. It does not explicitly differentiate itself from getPass or getPassBySerial, but its scope and endpoint mapping make the purpose unambiguous.

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?

It provides context by saying it lists passes for the current app and maps to GET /manage-passes, so an agent can infer when to call it. However, it does not mention alternatives such as getPass or getPassBySerial or state when not to use this tool, so selection guidance is only implied.

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