delete_api_key

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

The description discloses the destructive nature, the blocking effect on subsequent tool calls, and the OAuth authentication requirement. These go beyond the annotations (destructiveHint, idempotentHint) by adding context on consequences and prerequisites.

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?

Three sentences: first states purpose, second explains consequence, third mentions authentication. Extremely concise and front-loaded with the most important information.

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 simple delete operation with no parameters and annotations covering safety, the description fully explains the effect, consequence, and authentication requirement. It is complete given the tool's simplicity.

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?

The tool has zero parameters, and the description adds no parameter information, which is appropriate. With 0 parameters, the baseline score is 4, and the description meets that baseline.

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 'Delete your registered J-Quants API key' and 'Removes your API key from the server.' It uses a specific verb and resource, and distinguishes itself from sibling tools like register_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 explains that after deletion, subsequent calls will fail until a new key is registered via register_api_key, and it notes the OAuth 2.1 requirement. However, it does not explicitly state when not to use the tool or provide direct alternatives.

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