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

No annotations exist, so the description carries the full burden and does notable work: it discloses result-tier pricing (free up to 3 results, 0.005 USDC for the full list), names the payment channel x402_payment, and warns that sealed demands stay generalized. It still leaves unclear whether a call without payment silently truncates or errors, and whether 'index-only commercials' differs in reliability from open demands.

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 identity/scope claim front-loaded, pricing second, and the sealed-demand caveat last. Dense but every clause carries information; only 'index-only commercials' is jargon that costs the reader without paying back.

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 5-parameter, zero-required, zero-annotation tool with no output schema, the description covers cost and privacy but not the shape of what comes back: no mention of ranking, ordering, result fields, or what a 'generalized' sealed demand looks like. There is also no limit parameter, so the free/paid split is the only way to control volume and that mechanic is left half-explained.

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 20% (just instrument), and the description compensates for almost none of it. It ties the cost to x402_payment and implies skill via 'capability', but q, region, and instrument get no explanation at all — an agent cannot tell whether region is a filter code or free text, or how q differs from skill.

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 the resource precisely — open demands matching a capability — and anchors it against the sibling search_agents by calling itself the 'seller-side mirror'. An agent can tell it is a demand-discovery tool rather than an agent-discovery tool. The verb itself is only implicit (it never says 'lists' or 'returns'), which keeps it from a 5.

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?

'Seller-side mirror of search_agents' gives the governing context: use this when you are supplying a capability and looking for demand, use search_agents when you are looking for agents. It does not state explicit exclusions or prerequisites (e.g. whether you must already be registered as an agent), so it falls short of a 5.

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