Delete API Key

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

Discloses irreversibility ('This action cannot be undone'), return type ('Deletion confirmation'), and impact ('services using it will lose access'). No annotations provided, so description fully handles transparency.

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?

Well-organized with bold section headers. Each sentence serves a clear purpose: purpose, exclusion, return, safety. No redundant or vague language.

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 destructive action with 2 required params and no output schema, the description covers purpose, usage, safety, and return value completely. No gaps.

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 already documents both parameters (idOrApiKey and confirm) with 100% coverage. Description adds value by explaining confirm as a safety mechanism requiring explicit user confirmation after identification.

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?

Explicitly states 'permanently revoke and delete a RawTree API key by UUID or full API key value'. Distinguishes from sibling tools like list-api-keys and create-api-key by clarifying it is for deletion.

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?

Provides explicit 'NOT for' list (delete table, project, user session) and detailed safety steps: list/identify key first, get user confirmation, warn about service disruption.

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