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

Goes well beyond the readOnlyHint/openWorldHint annotations by naming the data source (landwatch.com public search pages via residential proxy), the exact billing model ($0.002 USDC per successful call via x402 on Base, Solana or Arc) and the key guarantee that failed calls are not charged. Cost and failure semantics are precisely the context an agent needs before invoking a paid tool.

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 layers pagination, source, and pricing without filler sentences. The long field enumeration is somewhat redundant given an output schema exists, but it reads as one dense sentence rather than padding.

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?

Covers source, scope limits, page ceiling, result size, cost, payment rails, and failure billing, while annotations and an output schema handle safety and return shape. Nothing an agent needs to call this correctly 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 all three parameters are already documented with examples. The description only adds the '25 per page' result size, which is mild added value; the page range and state/county examples merely restate the schema, so the baseline 3 applies.

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 — LandWatch land, ranch, farm and hunting listings for a US state or county — and enumerates exactly what comes back. An agent can immediately distinguish this land-focused tool from sibling residential/commercial listing tools like zillow or loopnet.

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?

Explicitly frames the use case as a state-level (optionally single-county) land query and discloses the pagination ceiling of pages 1–40 at 25 results per page. It doesn't name an alternative sibling or state when not to use it, but the land/ranch/hunting scope is a strong implicit router.

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