prufa_revoke_discovery_domain

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

No annotations; description discloses key behaviors: de-authorization, refusal of future discovery, tearing down disposable identities, response content, and idempotency. Lacks details on reversibility or error handling but adequate for its simplicity.

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?

Two short, front-loaded sentences. Every word adds value. No redundancy.

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 no output schema or annotations, description is largely complete. It explains the action, consequences, idempotency, and response. Could mention error conditions or prerequisites but not critical.

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%; description mentions response reports identities_torn_down but adds no extra meaning for the two parameters beyond what the schema provides (domain_id and idempotency_key). Baseline 3 applies.

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?

Clearly states 'De-authorize a discovery domain' with specific consequences (future discovery refused, disposable identities torn down) and idempotency. Differentiates from siblings like 'prufa_authorize_domain' (opposite action) and 'prufa_register_discovery_domain' (registration).

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?

Implied usage: use when you need to revoke a domain's authorization. The sibling 'prufa_authorize_domain' is the inverse. However, no explicit when-not or alternatives provided.

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