identity__revoke_agent

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

Without annotations, the description carries the burden of behavioral disclosure. It adequately states that the identity disappears from discovery (terminal) and the record is retained for auditability, indicating irreversibility and audit trail. However, it does not cover permission requirements or other side effects.

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 brief and to the point, but includes a group label prefix that may not be necessary. It efficiently conveys the core action and effect without extra fluff.

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 the tool is a mutation (revoke) with no annotations or output schema, and parameters lack schema descriptions, the description should provide more details such as valid parameter values, expected behavior, error scenarios, or confirmations. The current description is insufficient for complete understanding.

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 has 0% description coverage and the description adds no additional meaning to the parameters (did and agent_id). It does not explain how to use them, their roles, or differences, leaving the agent to infer from names alone.

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 verb 'Revoke an identity' with specific behavioral outcomes: disappears from discovery but record retained for auditability. This distinguishes it from siblings like register, resolve, discover, list, and describe.

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 implies usage for revoking an identity but does not provide explicit guidance on when to use this tool vs alternatives, nor does it mention prerequisites, when-not-to-use, or which parameter (did vs agent_id) to choose.

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