list_api_keys

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

No annotations are present, so the description carries the transparency burden. The phrase 'GET /api-keys' signals a read-only, non-mutating operation, and 'List' reinforces that it does not create or delete keys. It does not disclose response format, pagination, or auth requirements, but for a simple read-only listing the core behavior is conveyed.

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 a single front-loaded sentence with no filler. The endpoint parenthetical is compact and useful for wiring the call.

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 list operation with no output schema, the description supplies the essential information needed to invoke the tool: what it lists and the endpoint. It leaves out auth and pagination details, but those are not strictly required to make the call 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, so there is nothing the description needs to add beyond the empty input schema. The 100% schema description coverage and empty properties make parameter semantics a non-issue.

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 names the specific operation ('List'), the exact resource ('API keys'), and the HTTP endpoint ('GET /api-keys'), making the tool's purpose unmistakable. It also naturally distinguishes itself from the sibling tools create_api_key and delete_api_key.

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 or when-not-to-use guidance, and no alternatives are named. However, the verb-resource pairing implies the use case (retrieve existing API keys), and the sibling set only includes create/delete variants, so the intended usage is reasonably clear.

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