Create Global API Key

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

Description adds critical behavioral info: 'Returns metadata only — the key secret is never surfaced and cannot be retrieved via MCP.' This goes beyond annotations (destructiveHint=true, etc.) and clarifies a key safety aspect.

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 fluff, front-loaded with action and scope. Every sentence adds value, achieving maximum conciseness.

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?

Despite having an output schema and good annotations, the description omits parameter explanations, which is a gap. However, it covers the key behavioral nuance (secret not retrievable), making it minimally adequate for a creation tool.

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 coverage is 0%, and the description does not explain any of the 3 parameters (name, expires_at, request_id). The description adds no semantic value for parameters, leaving agents to infer from schema alone.

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 'Create a global (account-scoped) API key', specifying the action and resource. It also distinguishes from user-scoped keys (sibling 'create_user_api_key'), making the scope explicit.

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 implies usage for account-level API keys but does not provide explicit when-to-use vs alternatives or when-not-to-use. No exclusions or alternative tools are mentioned.

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