list_api_keys

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the description's job is light. It does not contradict annotations and adds the HTTP endpoint, but it provides no additional behavioral context such as what the return data represents. Given the annotations cover safety, a 3 is appropriate.

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 extremely short, which is good, but the phrasing 'Get api api-keys' is redundant and slightly garbled. The HTTP endpoint is informative, but the overall structure is minimal and not polished.

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?

Given the presence of an output schema and no parameters, the description is mostly complete. However, it does not explicitly state that this is a list/all operation (versus fetching a single key), and there is no get_api_keys_by_id sibling, so it is clear enough, but a brief clarification would help.

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, so the schema coverage is effectively 100%. The baseline for no parameters is 4; the description adds no parameter details because there are none, which is acceptable.

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 'Get api api-keys' which clearly indicates fetching API keys, but it is awkwardly phrased and does not explicitly distinguish from sibling operations like create, delete, or patch. It does include the HTTP endpoint which adds specificity.

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 provides no guidance on when to use this tool versus alternatives such as create_api_keys, delete_api_keys_by_id, or patch_api_keys_by_id. There is no mention of use cases, prerequisites, or exclusions.

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