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

The description discloses a critical behavior: 'The returned agent key is shown once.' This is not present in the schema or annotations (none provided). It warns the user to save the key immediately. Also, 'Register a handle once' hints at one-time nature, adding useful context.

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 sentences that immediately convey the action and the key warning. No wasted words, front-loaded with the purpose.

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 registration tool, it covers the essential behavior (key shown once) but does not describe the return format, purpose of display_name, or any post-registration steps. No output schema exists to fill this gap, but the tool's simplicity makes it adequate though not comprehensive.

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 description coverage is 0%, and the description does not compensate. It refers to 'a handle' but does not explain the display_name parameter at all. The schema defines handle with a regex pattern, but the description adds minimal semantic meaning beyond that.

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?

Title clearly states 'Register a bounty agent', and description specifies the verb and resource: 'Register a handle once.' It distinguishes from sibling tools like capability_register by focusing on agent handles.

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 explicit guidance on when to use this tool versus alternatives. The phrase 'Register a handle once' implies a one-time setup action, but it does not mention prerequisites, exclusions, or competing tools like capability_register.

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