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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond those annotations: the required scope `certs:manage`, the exact HTTP mapping to GET /manage-certs, and a warning about billing/rate limits and not inventing other paths. No contradiction with 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 with the core purpose, followed by scope and API mapping. The final sentence about 'Same PassFast HTTP API, billing, and rate limits' is somewhat vague about what 'same' refers to, preventing a perfect score, but overall every sentence earns its place.

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 read-only list operation with a single well-documented parameter and strong annotations, the description is sufficiently complete. It provides the required scope, HTTP mapping, and rate-limit caution, and no output schema is needed to call the tool correctly. Minor gap: no mention of response shape or pagination, but that is not critical for this 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?

The only parameter, x_app_id, is fully described in the schema with its override/default behavior. Schema description coverage is 100%, so the description does not need to add parameter-level detail; baseline 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 opens with a specific verb and resource ('List certificates') and clarifies it returns all certificates for the current app. This clearly distinguishes it from sibling certificate tools like deleteCertificate, uploadCertificate, and uploadP12Certificate.

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 implies usage when an agent needs the full set of certificates for the current app, but it does not explicitly state when to choose this tool versus alternatives, nor does it mention exclusions or direct the agent to a sibling tool. 'Returns all certificates for the current app' provides context but no explicit routing.

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