marketplace_revoke_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 of behavioral disclosure. It explicitly notes the permanent nature of the action ('permanently disabling its access'), which conveys irreversibility. However, it does not mention permissions beyond the schema's userAddress note, nor does it describe consequences like whether existing sessions/tokens are invalidated.

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 a single concise sentence that is front-loaded with the core action ('Revoke an API key') and includes the key detail ('permanently disabling its access'). No wasted words.

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 relatively simple revoke operation, the description covers the fundamental behavior but lacks contextual completeness. There is no mention of when to prefer this over marketplace_rotate_api_key, no guidance on the reason parameter's optionality, and no information about return values or output (though no output schema exists). The tool is understandable but leaves some 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 description coverage is 100%, so the baseline is 3. The description does not add any parameter-specific details beyond what is already in the schema; it only describes the action in general terms.

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 the tool's function: 'Revoke an API key, permanently disabling its access.' This specifies a distinct verb ('revoke') and resource ('API key'), and it differentiates from sibling tools like marketplace_rotate_api_key by emphasizing the permanent disabling of access.

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 such as marketplace_rotate_api_key or marketplace_pause_tool. It does not mention any prerequisites (e.g., ownership) or context for when revocation is appropriate.

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