Revoke API Key

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

Annotations already signal destructiveHint and idempotentHint, and the description adds meaningful behavioral context: 'Clients using that key stop working immediately' and '404 unknown id.' This goes beyond the annotation metadata and helps the agent anticipate the real-world effect and failure mode.

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 three short, information-dense lines with no filler. The core purpose is front-loaded, followed by prerequisite, auth, and error info. Every sentence earns its place.

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?

This is a single-parameter tool with rich annotations and low complexity. The description covers what the tool does, how to get the required id, auth requirements, immediate impact, and an error case. Nothing essential is missing for an agent to invoke it correctly.

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 100%, and the schema already describes `id` as 'API key id as returned by `ethora-api-key-create` / `ethora-api-key-list`.' The description repeats this prerequisite without adding substantially new parameter semantics, so the baseline score of 3 is appropriate.

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 opens with a specific verb and resource: 'Revoke one of the current user's API keys by id.' It clearly scopes the operation to the current user and distinguishes it from related key tools like create and list by the revoke action. The wording is unambiguous and immediately tells the agent what the tool does.

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 specifies the prerequisite for using the tool: a key id from `ethora-api-key-list` or `ethora-api-key-create`. It also states auth requirements and a likely error condition. It doesn't explicitly name alternatives or say when not to use it, but the context is clear enough for a revoke operation.

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