keys_create

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

With no annotations, the description carries the full burden. It notably discloses that the key is shown only once, a crucial behavioral trait that the agent must know. However, it does not mention authorization requirements, side effects on existing keys, or any rate limits, so it only partially covers the behavioral spectrum.

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, focused sentence of 8 words. The core purpose is front-loaded, and every word contributes meaning. There is no redundancy or filler.

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?

The tool is simple, but the description is incomplete. It lacks any explanation of the 'name' parameter, so the agent cannot confidently decide whether or how to populate it. Without an output schema, the agent also does not know what the tool returns. The 'shown once' note is helpful but not enough for full operational clarity.

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 schema has one optional 'name' parameter with zero description coverage. The tool description does not mention this parameter at all, so it adds no meaning beyond the schema. An agent has no idea what 'name' represents, how to format it, or whether to include it.

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 ('Mint a new aa_ API key') with a specific verb and resource. The 'shown once' detail adds a distinct characteristic that separates it from sibling tools like oauth_client_create or create_login_link. An agent would immediately understand this tool creates an API key with a specific prefix.

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 tool versus the sibling tools, when not to use it, or any prerequisites. The description only states what the tool does, leaving the agent to infer the appropriate context on its own.

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