create_api_key

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

With no annotations provided, the description carries the full behavioral disclosure burden. It reveals the critical behavior that the full key is returned exactly once and cannot be retrieved again, and instructs the agent to surface it immediately. This is essential operational context, though it doesn't detail other side effects like rate limits or whether existing keys remain valid.

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 sentences with no filler. The core action is front-loaded, followed by the critical one-time-display warning and the separation best practice. Every sentence earns its place and the description is easy to parse quickly.

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 tool with zero parameters and no output schema, the description covers all essential context: what it does, the one-time key disclosure, and how the user should handle the key. There is no missing information an agent would need to invoke this tool correctly and guide the user.

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 input schema has zero parameters, so there are no parameter semantics to describe. The description adds context about per-environment key usage, which is more guidance than parameter explanation. Baseline of 4 is appropriate for a schema with no parameters.

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?

Description states the exact action and resource: 'Create a new API key.' This clearly distinguishes it from siblings like list_api_keys and revoke_api_key, which have different verbs and resources. No ambiguity about what the tool does.

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 actionable guidance: surface the key immediately because it's shown only once, and mint separate keys per environment/service rather than sharing one. It doesn't explicitly name alternatives or when not to use this tool, but the context is clear and no competing sibling creates API keys.

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