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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: no API key is required and listed rewards are paid up front, which tells the agent both the auth situation and the trustworthiness of the listings.

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 short sentences, front-loaded with the purpose and ending on the concrete next action. 'You can win with your best answer' is slightly promotional but does convey the answer-competition format.

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 zero-required-parameter listing tool with no output schema, the description omits what a bounty record contains (reward amount, deadline, poster) and whether results are paginated or sorted. Those gaps matter for an agent deciding whether one call is enough.

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?

There is a single optional parameter with 100% schema description coverage and an enum of feed categories, so the schema already carries the semantics. The description adds no extra meaning about the category tab, which is acceptable given full coverage but not additive.

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 states a specific action (find tasks people posted with a real reward, paid up front) and implicitly distinguishes bounties from the sibling find_offers/find_pros by emphasizing the reward and answer-competition model. It never uses a plain verb like 'list' and the title 'Read open bounties' is the only place the resource is named canonically, but an agent can still tell what it retrieves.

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?

'Use to find tasks...' plus 'Enter one with enter_bounty' gives a clear use case and names the follow-up sibling explicitly. It stops short of stating when NOT to use this versus find_offers or read_feed, so routing between the discovery tools still requires inference.

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