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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only the underlying REST route mapping (GET /v1/organizations/{id}/api-keys), and says nothing about pagination, whether key secrets are masked in output, or permission requirements for reading an org's keys.

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?

Two short fragments, the purpose front-loaded ahead of the endpoint reference, with no filler. Nothing needs to be trimmed and the key fact arrives first.

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 single-parameter read tool with full annotation coverage, this is mostly sufficient, but there is no output schema and the description never indicates what a returned key record contains (e.g., masked secrets) or whether results are paginated. Those gaps are the only thing an agent would still have to discover by calling it.

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% for the single required parameter, so the baseline is 3. The description only re-encodes the parameter as {id} inside the route path and adds no clarification about whether it is an org slug, ID, or name.

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?

States a specific verb+resource+scope: 'List API keys for an organization', which tells an agent exactly what it retrieves. It does not name or differentiate against nearby siblings such as ai.keys, keys.get, or apikey.revoke, so an agent must infer that this is the org-scoped key enumeration and the other is the mutation.

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 explicit when-to-use guidance and no exclusions. The verb 'List' implies a read enumeration, but with siblings like ai.keys, keys.get, and apikey.revoke present, the description never says when this tool is the right choice versus those.

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