List API Keys

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

With no annotations, the description carries the full behavioral burden and offers almost nothing: it does not say whether full secret key values are returned or masked, whether results are paginated/ordered, or what authorization level is required. For an API-key tool, secrecy of returned material is exactly the behavior an agent needs disclosed.

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?

A single tight sentence with the resource front-loaded and no filler. It is efficient, though its brevity edges into under-specification rather than optimal density.

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 zero-required-parameter list tool with fully documented params, the core is covered. But with no annotations and no output schema, the description should at least hint at what is returned and at pagination behavior, and it does neither.

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% – both page and limit are documented in the schema with defaults and bounds. The description adds nothing beyond that, which is acceptable but not additive; baseline 3 applies.

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 and resource ("List all API keys") scoped to the Emailit account, which is enough to distinguish it from get-api-key, create-api-key, update-api-key and delete-api-key. It stops short of explicitly naming those siblings, but the list-vs-single distinction is 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?

There is no guidance on when to use this versus get-api-key, nor any note about pagination strategy, page-size tradeoffs, or preconditions such as account/admin permissions. The listing semantics imply the use case, but nothing in the text directs the agent's choice.

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