rotate_developer_key

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

Discloses key behaviors beyond annotations: atomic operation, session requirement (AAL2), and one-time return of plaintext. Annotations provide idempotentHint=true, which aligns; no contradiction.

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 concise sentences that front-load the atomic action and critical constraints (AAL2, once-only return). No wasted words.

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 parameter count of 2 with full schema coverage and no output schema, the description adequately explains the atomic rotation, session requirement, and return behavior.

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?

Input schema has 100% coverage with explicit descriptions for both parameters (key_id and name). Description does not add further details, so baseline 3 is appropriate.

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 clearly states the action (rotate) and resource (developer key), with verb+resource structure. It distinguishes from siblings like create_developer_key and revoke_developer_key by emphasizing atomic rotation (revoke old, mint new).

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?

Explicitly mentions prerequisite (AAL2 session) and a critical caveat (new plaintext returned ONCE ONLY). Does not explicitly contrast with create/revoke, but the context is sufficient for an agent to infer when to use rotation vs separate revocation/creation.

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