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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral value beyond that: it is free to call, and it discloses the verdict taxonomy and that gating signals (KYC, human claim, self-custody) and escrow payout data are included, telling the agent what judgment the data supports.

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?

A single dense sentence, front-loaded with the cost signal and then the content categories. The colon-list is information-dense rather than padded, though it reads as a feature dump that could be trimmed slightly.

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?

With an output schema present, the description need not explain return shape, and with zero parameters there is no input contract to document. It covers scope and content categories well; the only gap is freshness/source recency, which an agent making a money decision might reasonably want.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to carry; baseline is 4. Nothing in the description misdescribes the (empty) input contract.

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 resource and enumerates its exact contents: a scorecard of bounty boards, task markets, audit contests and x402 sell-side, with a named verdict taxonomy. An agent can distinguish this from settled_income_listings and settled_income_check without opening a schema.

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?

"Free." signals no credit cost, which is a mild usage hint, and the resource makes the intended context (an agent looking for venues that actually pay) fairly obvious. However, it never says when to use this versus settled_income_listings or settled_income_check, and gives no exclusions.

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