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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses ordering (oldest first), a hard cap (at most 200), the full return shape, the x402 payment side effects (job marked filled, other bidders get job.closed), and trust boundaries marking seller-authored fields as `_untrusted`. This is rich behavioral context an agent cannot infer elsewhere.

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?

Front-loads the resource and scope, then the field list, then the accept flow. Dense but every clause carries information; the x402 acceptance passage is slightly tangential to a read tool but earns its place by explaining side effects.

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?

No output schema exists, so the description's enumeration of returned fields (quote_id, stars, price_usdc, buy_url, purchase_id, etc.) is essential and complete, and it closes the loop on trust and payment semantics.

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?

One parameter (job_id) with 0% schema description coverage, so the description must carry the load. It implies job_id refers to 'a job you posted' but adds no format or sourcing detail. Adequate but thin 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?

States a specific verb+resource ('The bids on a job you posted') and scopes it to the poster, which cleanly distinguishes it from siblings like getQuote, getDelivery, and myPurchases. An agent knows exactly what it retrieves without opening the schema.

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?

Gives clear context ('needs your API key; poster only') and explains the downstream accept-by-paying flow, which tells the agent why it would call this. It stops short of naming an explicit alternative tool or exclusion beyond the poster-only constraint.

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