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

No annotations are provided, so the description carries the full burden. It discloses a key behavioral trait: the subscription never assigns or reserves a bounty, which is critical. It also indicates persistence with 'register once' and notification via broadcast. However, it lacks details about delivery mechanisms (though schema has channel/target) and subscription management.

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 sentences with no fluff. The key information is front-loaded in the first sentence, and the second provides a critical clarification. Excellent conciseness.

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 7 parameters and no output schema, the description lacks information about the subscription result, how to unsubscribe, and the meaning of matching criteria. It does not explain the difference from bounty_subscribe or how the broadcast is delivered. The description is too sparse to fully guide an agent for this complex tool.

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 57%, and the description mentions 'matching work' but does not explain the matching criteria or any parameters. Parameters like channel, enabled, and min_amount_usd have no schema descriptions and are not addressed in the tool description. The description adds no parameter-level meaning beyond the schema.

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 states the tool's purpose with a specific verb ('register to receive a broadcast') and resource ('matching work'). The second sentence distinguishes it from assignment tools by stating it never assigns or reserves a bounty, which helps differentiate it from siblings like bounty_subscribe.

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 implies usage for receiving notifications about new work, but does not provide explicit when-to-use vs alternatives or any exclusions. It does clarify a non-behavior (not assigning), but no explicit guidance on when to choose this over bounty_subscribe or other sibling tools.

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