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

Beyond the readOnly/openWorld annotations, the description discloses the commercial model: $0.002 USDC per successful call via x402 on Base/Solana/Arc, with failed calls not charged. That cost and payment-path disclosure is real behavioral context an agent cannot get from annotations, and it also clarifies the 30-newest-reviews cap.

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 the resource and geography, then the field inventory, then the parameter rule and price. It is dense and waste-free, though the long return-field enumeration partially duplicates what the existing output schema already exposes.

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 read-only, three-parameter lookup with an output schema, the description covers everything an agent needs: source, geography, identifier format, payload contents, and cost/billing behavior. Nothing material is missing.

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 100%, so the baseline is 3. The description echoes the schema's company example (kfc-432299) and implies the limit ceiling via 'the 30 newest reviews', but adds essentially no new meaning about the country toggle or the limit string type.

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 (employer reviews from SEEK) and immediately scopes it geographically to Australia/New Zealand, which separates it from generic review siblings like b2b_trustpilot_reviews, b2b_clutch_reviews or b2b_g2_software_categories. It also enumerates the returned payload, so an agent knows exactly what data it gets.

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 only implied: an agent can infer it should call this for Australia/NZ employer-review data, but the description never states when to use it instead of the sibling review or company-benefits tools, nor any prerequisites (e.g. that a SEEK slug must be resolved first). Guidance is adequate but leaves the routing decision to inference.

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