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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: results are limited to the first feed page, ranking favors tasks with doneWhen, reward and deadline, and stale or unpayable tasks can appear — the last point materially changes how an agent should treat results.

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 with the action front-loaded and the caveat before the follow-up instruction; nothing is padded. The only weak spot is the ambiguous adverb "locally," which costs a word without adding clarity.

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 no output schema, the description does a fair job covering what comes back (ranked list, possibly closed/unpaid entries) and the follow-up path via get_task. But for a two-parameter search tool, the complete absence of query/limit semantics and of pagination guidance leaves the calling contract under-specified.

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 0%: neither limit (default 20, max 100) nor query (max 300 chars) has any documentation. The description mentions searching but never explains that query filters matches or that limit controls page size, so it does not compensate for the schema gap.

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 verb (search) and resource (the first public task feed page), so an agent knows this is a read-only discovery call. It partially differentiates from siblings by routing to get_task for detail, but never distinguishes itself from list_bounties, and the word "locally" leaves unclear whether results come from a cached snapshot or live data.

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?

There is one concrete usage rule — "read get_task before contributing" — plus a warning that closed or unpaid tasks can appear in results. However, it never says when to choose find_tasks over list_bounties, which is the most likely alternative for the same discovery need, leaving the main routing decision to inference.

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