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

Annotations already declare this a safe, idempotent, read-only, closed-world read, so the burden is lighter. The description still adds real value beyond them: authentication is required, suspected honeypots, dead and human-only listings are filtered out by default with a named opt-out, and each row carries heuristic scan flags with reasons plus an on-chain payout record.

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 the hard prerequisite ('Pass required') front-loaded, followed by one dense but purposeful sentence covering scope, provenance, payload and default exclusions. Efficient, though the second sentence is a long field list that could be trimmed given the schema lists the same fields.

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?

An output schema exists, so return values need no explanation, yet the description helpfully previews the key fields. Auth, defaults, filtering rules and the opt-out are all covered; the only missing piece is how this call relates to its sibling listing/venue tools.

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% (8 params, each documented, two with enums), so the schema carries the parameter semantics and a 3 is the baseline. The description only restates the include_honeypots and agent-access behavior in prose, without adding syntax, defaults, or interaction rules the schema does not already cover.

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 names a clear resource - open bounties/tasks an agent can actually work on, sourced from sanctioned venue APIs - and enumerates the payload (reward, access policy, gating, honeypot flags, trust score, payout record). It does not explicitly contrast itself with the nearest siblings such as settled_income_venues or settled_income_check, so an agent still has to infer the split from the names.

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 precondition ('Pass required') and the default filtering behavior, including the override condition ('unless include_honeypots is true'), which tells the agent when to flip the flag. There is no explicit routing guidance telling the agent to prefer settled_income_venues for venue slugs or another sibling for a different query type.

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