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

Adds meaningful behavior beyond annotations: it broadcasts matching work, announces pots at $0 before pledges, filters via min_amount_usd, and explicitly does not reserve or assign. That compensates for the non-obvious semantics of a subscription mutation with idempotentHint=false.

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 tightly packed sentences with no waste. The core purpose is front-loaded, and every clause adds actionable semantics about pot announcements, filtering, and non-reservation.

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 7-parameter subscription tool with no output schema, the description covers the key behavioral outcome and a critical exclusion. It is slightly incomplete on channel and enabled semantics and does not describe the alert payload format, but the essentials for correct invocation are present.

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 57%, with channel, enabled, and min_amount_usd undocumented in the schema itself. The description compensates for min_amount_usd by explaining that values above 0 skip $0 pots, but it says nothing about channel or enabled, leaving a meaningful gap.

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?

States a specific action (register once) and a concrete outcome (broadcast when matching work is posted, including $0 pot openings). An agent can tell what it does, though it does not explicitly distinguish itself from the sibling bounty_subscribe tool.

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?

Gives a clear usage context ('register once') and an explicit boundary: 'This never assigns or reserves a bounty,' which tells the agent this is notification-only. It does not name when to prefer bounty_subscribe or other alert mechanisms, so routing between siblings is left to inference.

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