revoke_agent_trust

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

Description mentions 'immediately terminate,' implying irreversibility and speed, but lacks details on permissions required, side effects, or whether the action is destructive. No annotations are provided, so the description carries full burden and is insufficient.

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 extremely concise (4 words) but at the cost of completeness. It is front-loaded but lacks structure and contextual information.

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 simple one-parameter tool with no output schema, the description provides minimal context. Given the large sibling set, more context would improve completeness.

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 covers the sole parameter with a clear description. The tool description adds no further semantic value beyond what the schema already provides.

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 states 'terminate a trust relationship,' which clearly indicates the tool's action and resource. However, it does not differentiate from sibling tools like 'evaluate_agent_trust' or 'negotiate_agent_trust,' which also operate on trust relationships.

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 this tool versus alternatives. Given many sibling trust-related tools (e.g., evaluate_agent_trust, negotiate_agent_trust), explicit usage context is missing.

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