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

Annotations already define readOnlyHint, idempotentHint, and destructiveHint, so the description need not repeat them. It adds value by specifying the required organization scope and warning against inventing paths. This goes beyond annotation coverage and gives operational context.

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, with a clear lead sentence, a bullet for scope, and a brief note on API mapping and constraints. Every line earns its place without fluff.

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 list operation, the description includes necessary operational context: scope, endpoint mapping (GET /manage-keys), and cautions about rate limits and path invention. Nothing essential is missing for an agent to call it correctly.

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 has zero parameters, and per rubric the baseline is 4. The description correctly avoids speculative parameter details. No additional semantics are needed.

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 clearly states the action (List) and resource (API keys) with explicit scope ('current organization'). It is distinct from sibling tools like createApiKey, deleteApiKey, and revokeApiKey, making it 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?

The description defines when to use the tool (to list all API keys for the organization) and adds a required permission scope (`org:manage`). It doesn't explicitly contrast with sibling list operations like listCertificates or listImages, but the resource type is obvious. The technical mapping and rate-limit note provide additional context.

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