revoke_witness_transfer

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the tool is a mutation but not flagged as destructive. The description adds no behavioral context beyond 'revoke or supersede'—no mention of side effects, auth requirements, or data impacts. With annotations present, the bar is lower, but the description still fails to enrich understanding.

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 mostly concise with one effective sentence about the purpose. However, the second word 'Free.' is extraneous and does not contribute to tool understanding, slightly reducing efficiency. It earns its place but could be improved.

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?

With 8 parameters and no output schema, the description is insufficient. It fails to explain return values, side effects, or when this mutation is appropriate. The tool's complexity demands more context than provided.

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 input schema already describes each parameter in detail. The description adds no additional parameter meaning. Baseline of 3 is appropriate because the schema does the heavy lifting.

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 purpose: 'Revoke or supersede a witness transfer for future continuity decisions.' The verb 'revoke or supersede' is specific, the resource 'witness transfer' is precise, and the tool is distinct from siblings like 'accept_witness_transfer' or 'transfer_witness'.

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?

No guidance on when to use or not use this tool. There is no mention of prerequisites, alternatives, or scenarios where revocation is appropriate. The phrase 'Free.' is irrelevant and does not aid usage decisions.

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