delete_api_key_by_id

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

No annotations are provided, so the description must disclose behavioral traits. It only labels the operation as a 'mutation', which implies a write, but does not mention irreversibility, permission requirements, side effects, rate limits, or any other safety-relevant details. This is inadequate for a destructive operation.

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 concise, consisting of one line with a clear header ('API Keys · mutation deleteApiKeyById') and an example. It is front-loaded and contains no redundant filler, though the formatting with '·' is slightly unusual.

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?

Given the lack of annotations and output schema, the description should compensate by explaining the deletion's effects, when to use it, and how it differs from other deletion tools. It provides none of that, leaving the agent with insufficient context for safe and correct invocation.

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 description coverage is 100%, so the schema already describes all three parameters. The description adds an example variables object but omits the 'customer_slug' parameter and does not explain the meaning of 'id' or 'user' beyond the schema's GraphQL type hints, adding minimal value.

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 identifies the operation as a mutation to delete an API key by ID via the phrase 'deleteApiKeyById', which is clear and matches the tool name. However, it does not explicitly describe the action in a full sentence or differentiate from the sibling tool 'delete_api_keys', which may handle bulk 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?

The description provides no guidance on when to use this tool versus alternatives like 'delete_api_keys', no prerequisites, and no exclusions. It only lists variables and an example, leaving the agent without contextual information for selection.

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