apikeys_rotate_api_key

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

Discloses that new key is returned once and instructs to store immediately, but doesn't explicitly state that old key is revoked or highlight side effects. No annotations provided to supplement.

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, no redundant information, core information presented upfront and efficiently.

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?

Covers purpose and return behavior, but omits error conditions, permissions, and fate of old key. Output schema exists but could be complemented by more context.

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 parameter 'current_key' lacks description; description adds instruction to pass key via header but doesn't clarify parameter semantics. With 0% schema coverage, more detail needed.

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?

Clearly states it revokes current API key and issues replacement, distinguishing from sibling tools like apikeys_generate_api_key and apikeys_revoke_api_key by combining both actions.

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?

Implied usage from action description, but no explicit when-to-use vs alternatives or prerequisites mentioned.

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