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

Annotations only declare readOnly/openWorld; the description adds materially new behavior: a per-call price of $0.02 USDC, the x402 payment rails (Base, Solana, Arc), and the guarantee that failed calls are not charged. It also discloses the retrieval path ('public search pages via a rendering residential proxy'), which pre-warns about latency, and caps results at 20 per page over 5 pages.

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-loaded with source and returned fields, then cost and payment mechanics — a logical order with no filler sentences. The return-field enumeration runs long and partly duplicates the output schema, but nothing is wasted.

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 paid, proxied scrape tool the description covers coverage limits, pricing, payment path, failure billing, and data provenance; an output schema exists so return values need not be explained in depth. An agent has everything needed to decide, budget, and call it 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 100%, so all three parameters are already documented, making 3 the baseline. The description only re-confirms the keyword-and-location query shape and restates the page-1-to-5 bound plus the 20-results-per-page cap, without adding syntax or format guidance beyond the schema.

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 and resource ('ZipRecruiter job search (US)'), enumerates exactly which fields come back (title, company, location, work setting, pay text, benefits, link), and pins the scope to 20 per page across pages 1-5. Because the sibling set is a list of other named job boards, the ZipRecruiter identity alone makes it distinguishable without opening a 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?

The description implies context ('US', keyword + location query) but never states when to pick this over jobs_indeed, jobs_linkedin_jobs, jobs_glassdoor, or jobs_multi_job_board, and offers no exclusions or prerequisites. Usage is inferable from the board name rather than spelled out.

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