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 add real behavioral content: the pool-selection ladder (seller pool, class pool with per-worker cap, protocol vault, else none), that the buyer never picks, and a why[] for refusals/downgrades. It says nothing about idempotency, auth/permissions, or error behavior for the call itself, so it stops short of full disclosure.

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?

One enormous run-on sentence packed with nested parentheticals overloads the reader; the front-loaded purpose is buried under the return-field enumeration. It is dense rather than concise, and structure does not help an agent parse quickly.

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?

Because there is no output schema, enumerating the returned terms (pool, pool_free, auto_complete_eligible, record, rails, why[]) is genuinely useful completeness. However, input semantics for a 6-parameter tool are largely missing, and the two aspects roughly balance out to a minimum-viable 3.

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 only 17% and the description clarifies just two things: price is in smallest units of the settlement token and tenant 'moonbeam' quotes against GLMR pools on Base. seller, class, price_usdc, and chain_id are left undocumented, so the description fails to compensate for the coverage 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?

The opening ('the terms one job would settle on for a seller at a price') does convey a quote/settlement-terms computation, but the label 'The matcher' is jargon and overlaps heavily with siblings like taifoon_match and taifoon_offers without saying how this differs. An agent can guess the purpose but is not given a crisp verb+resource statement.

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, when-not-to, or alternative-tool routing despite many plausibly overlapping siblings (taifoon_match, taifoon_offers, taifoon_grid_pool). The only implied usage is that it is a pre-settlement quote for a seller.

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