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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: results are pre-funded ('payout already held') and carry a proof requirement, which shapes how an agent should interpret the returned tasks. It says nothing about read-only safety, ordering, pagination, or the 50-item cap, so coverage is partial.

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 tight sentences, zero filler, with the core identity ('funded tasks people can do right now') and the trust signal ('payout already held') front-loaded before any secondary detail.

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 four-parameter discovery tool with no annotations and no output schema, the description conveys what the result set means but omits return shape, ordering, pagination, and the undescribed limit parameter. It is adequate to justify calling the tool but incomplete on how to call it well.

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 75% (q, type, category documented; limit undescribed), so the schema already does most of the work. The description adds no filtering semantics, no default limit behavior, and no example values beyond what the schema provides, leaving the score at baseline.

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 and resource ('List funded tasks') and adds a qualifying scope ('funded', 'people can do right now'), which distinguishes it from the single-task sibling get_task and the write-oriented post_task/fund_task. It never names a sibling, but the list-vs-mutate distinction is clear from the phrasing.

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 no explicit when-to-use guidance or reference to alternatives such as get_task for a single task. The phrase 'people can do right now' weakly implies a discovery/browse use case but leaves the agent to infer it.

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