Manage Agent Identity

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

The description adds significant behavioral context beyond annotations: it specifies that whoami involves no network or secrets, claim is one-way binding, and logout does not revoke on relay. This aligns with the destructiveHint annotation and provides clear safety information.

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 concise and front-loaded with 'Agent identity + binding.' It uses a bullet-like structure with pipes for readability. While packed with information, it could be slightly more streamlined, but it remains clear and efficient.

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 complexity of three actions and no output schema, the description lacks details about return values or expected outcomes (e.g., what whoami returns in detail). It provides enough context for usage but not full completeness for an agent to understand all outputs.

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%, so baseline is 3. The description enhances parameter semantics by explaining when the 'code' parameter is required (for claim) and by expanding on the meaning of each action enum value. This adds value beyond the schema descriptions.

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 identifies the tool as managing agent identity and binding with three distinct actions (whoami, claim, logout). Each action's purpose is specifically described, and it distinguishes from the sibling 'key' tool by noting that logout does not revoke on relay.

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 explicitly states when to use this tool (for agent identity management) and provides guidance for each action, including when not to use logout (revoke via key tool). It also clarifies that claim is one-way and requires a code from Settings UI.

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