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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description goes further with genuinely non-derivable traits: data is refreshed hourly (freshness limit), rewards are unverified claims, and counts are a lower bound on long issues with the row saying so. It does not, however, mention pagination behavior or rate limits.

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?

Purpose and the row contents are front-loaded before the workflow guidance, and no sentence is pure filler. The body is a single long clause-chained sentence, which is dense and slightly harder to scan than a short bullet-style breakdown.

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?

There is no output schema, so the description must carry the return-value burden, and it does: it enumerates the meaningful row fields (open PRs, claimers/assignees, rewarded label, stated reward, repo rewarded count), the sort order, and the caveats. An agent has enough to call and interpret it correctly.

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 100%, so the baseline is 3. The description adds interpretive meaning beyond the schema — 'repository_pays' is 'the only public sign that it pays' and the crowd/reward counts are explained as claims and lower bounds — which helps an agent interpret filter results, though it does not add format or syntax detail.

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 gives a concrete verb+resource: 'Read-only list of open GitHub issues that carry a bounty label,' and immediately characterizes the rows (open PRs, claimers, rewarded label, reward in label/title). It clearly separates itself from siblings like look and claim by being the discovery step, not the verification or claim step.

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?

It states the workflow explicitly: 'Use it to choose work; then call look on the issue you picked for the live light, and claim before you start.' That names the alternatives (look, claim) and the condition ordering, leaving nothing to inference.

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