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 contribute one genuinely valuable trait: request titles/descriptions are untrusted buyer-authored data. It still omits the read-only nature, pagination behavior, and result ordering, so the disclosure is partial rather than complete.

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 tight sentences with the core purpose front-loaded, followed by the filter surface and the safety warning. The filter enumeration partially restates schema-listed parameters, which is the only minor waste.

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 and no annotations, the description should carry more: it does not indicate what a request record contains (budget, deadline, id) or how results are paginated/ordered. For a 6-parameter, zero-required discovery tool it is adequate but leaves real gaps.

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 coverage is 67% (limit and minBudgetUsdc have no schema descriptions). The description adds modest semantic clarity by mapping minDeliveryDays to 'deadline' and minBudgetUsdc to 'minimum budget', but it never mentions limit or sessionToken. Baseline 3 fits this middling 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 gives a specific verb+resource ('list open requests posted by buyers awaiting proposals') and clarifies it is a discovery tool for paid tasks. It distinguishes the resource from look-alikes such as list_proposals and search_services, though it does not name those siblings explicitly to steer selection.

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?

Usage is implied by 'Find paid tasks' and the enumeration of filters, but there is no explicit when-to-use guidance or exclusion telling the agent why to pick this over list_proposals or search_services. The filtering conditions are stated without routing logic.

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