Permanently revoke THIS agent using its API key as the Bearer token. Use when you discover (at any time) that paired_with is not your owner’s account and cancel_registration no longer works. The key stops working immediately; call register_agent to start over.
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | Yes | Must be true — revocation is immediate and irreversible |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that revocation is permanent, immediate, and makes the key stop working. While annotations only indicate readOnlyHint=false, the description goes further by explaining the irreversible effect and the auth mechanism (API key as Bearer token), adding significant value beyond annotations.
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?
Three concise sentences, each adding necessary information: the action, the condition to use it, and the consequence/next step. No filler or redundant wording.
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 tool with one param and no output schema, the description covers the purpose, usage condition, effect, and recovery path. It lacks only minor details like return value or error cases, but these are not critical given the tool's simplicity.
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 single parameter (confirm) is fully described in the schema itself. The tool description does not add additional parameter semantics, but does not need to because the schema already provides complete meaning.
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 uses the specific verb 'revoke' and identifies the resource as 'THIS agent', clearly distinguishing it from sibling tools like cancel_registration. It also explicitly contrasts with cancel_registration, making its unique purpose unmistakable.
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?
Explicitly states when to use: 'when you discover ... that paired_with is not your owner's account and cancel_registration no longer works.' It also provides an alternative next step ('call register_agent to start over'), giving clear directional guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct role in the registration lifecycle or notification sending. register_agent starts, check_registration polls, cancel_registration revokes within a limited window, revoke_self permanently revokes with the API key, and yo sends the notification. Overlap between cancel and revoke is clearly delineated by time and authentication context.
The core tools follow a verb_noun pattern (register_agent, check_registration, cancel_registration, revoke_self). The tool 'yo' is an exception but functions as a domain-specific verb, and the naming is otherwise predictable. Minor inconsistency exists between 'agent' and 'registration' but does not hinder comprehension.
With five tools, the server is well-scoped for the Yo integration. Each tool serves a necessary function in the registration and notification flow without redundancy or bloat. The count is appropriate for the domain.
The tool set covers the complete lifecycle: registering an agent, checking status, canceling/revoking, and sending a Yo. There are no obvious missing operations for the intended domain, and the flow from registration to notification is fully supported.