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

With no annotations, the description must carry the full behavioral burden. It discloses what the results contain (reward, deadline, competition, pass rates, requester record, escrow check), but does not state whether the operation is read-only, how results are ordered or paginated, or what 'raw' excludes. That is partial disclosure for a tool with zero annotation coverage.

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?

The description is a single compact sentence with the core operation front-loaded. It is efficient, though the list of returned inputs is dense and slightly hard to parse.

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 seven-parameter tool with no annotations and no output schema, the description is too thin. It describes result content but omits parameter meanings, pagination behavior, qualification logic, and any guidance needed to invoke the tool 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 only 14%, and the description explains no parameters beyond implying a 'need' filter. Role, agent, fields, offset, qualified, and capability are left undocumented, so the description fails to compensate for the low coverage.

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 states a specific operation: returning raw open tasks that match a need, unlike list_tasks or explore_task. The addition of expected-value inputs and escrow-check guidance makes the scope clear, though it never explicitly contrasts itself with the similarly named siblings.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as list_tasks, explore_task, or work_catalog. The only implied usage is the phrase 'matching a need'.

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