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

No annotations exist, but the description discloses behavioral specifics: sealed ciphertext is destroyed, authorization is required. However, permissions, error handling and reversibility/irreversibility are not discussed.

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?

Single concise sentence with no redundant exposition; defines the core action and the side effect.

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 credential revocation tool, the description is clear on outcomes and side effects (destroys sealed cipher). But context for nonexistent IDs or invalid permissions is absent; no return schema exists, though the action is straightforward.

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?

The input schema is 100% covered and adds minor context that id is a credential id (UUID). The description does not explain parameter value behaviors, but there is only one parameter.

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?

Description uses specific verb 'Revoke' plus resource 'venue credential' and explicitly states the sealed ciphertext is destroyed. This is unambiguous and distinct from sibling tools that revoke delegations.

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?

Clear command to revoke a credential, but does not explicitly state when to use this vs. alternatives like revoking a delegation, nor any prerequisites such as the credential needing to exist.

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