create_developer_key

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

Discloses critical trait: plaintext key returned only once (save immediately). Annotations (readOnlyHint=false, destructiveHint=false) are consistent; description adds value by warning about one-time exposure and linking to authentication flow.

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: first states purpose and key pattern, second covers prerequisites and critical warning. Every sentence adds value, no 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?

Covers essential aspects: purpose, prerequisite, key pattern, one-time return warning. No output schema exists but description provides adequate guidance for a simple creation tool; missing details like max keys per user are non-essential.

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 covers 67% of parameters with descriptions; description adds no additional parameter info beyond what schema provides, so baseline score of 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?

Description clearly states the tool mints a new API key with specific prefix patterns (ac_live_* or ac_test_*), distinguishing it from siblings like revoke_developer_key and rotate_developer_key.

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 requires AAL2 session (enroll_mfa + verify_mfa first), providing clear precondition. Implicitly differentiates from key revocation/rotation by specifying 'Mint a new', though no explicit when-not-to-use guidance.

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