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 burden and clearly discloses the critical behavioral trait that the secret key is only shown once. However, it does not mention other traits like idempotency or auth requirements.

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?

The description is extremely concise, with three sentences plus an 'Args:' section, front-loading the purpose and the critical storage note, with no extraneous content.

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?

The description covers the essential behavior and parameters, but it lacks explicit mention that the project_id must refer to an existing project, which is a reasonable expectation for a create 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?

Despite 0% schema description coverage, the description explains both parameters in plain language: 'project_id: The project ID to create the key for.' and 'note: Optional label for the key,' adding necessary context beyond the schema.

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 explicitly states 'Create a new API key pair (pk/sk) for a project,' using a specific verb and resource, which clearly distinguishes it from siblings like create_project or delete_api_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?

The description provides a usage hint about storing the secret key immediately but does not explicitly state when to use this tool versus alternatives like list_api_keys or delete_api_key, nor does it mention prerequisites (e.g., project must exist).

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