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

Goes well beyond the readOnly/openWorld annotations by disclosing the data source (loopnet.com public search pages via a residential proxy) and a precise billing model: $0.002 USDC per successful call via x402 on Base/Solana/Arc, with failed calls free. That cost-on-success detail is exactly the kind of 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?

Two sentences, purpose front-loaded, pricing last. The long field enumeration is mildly redundant given an output schema exists, but the rest is dense and free of filler.

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?

With a full output schema and annotations, the description covers the remaining gaps: source, coverage limits (US cities only, pages 1-20), and the payment model. Only the lack of routing guidance against similar commercial-listing siblings keeps it from a 5.

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 every parameter is already documented with defaults and examples. The description restates the page range and deal types but adds no syntax or constraint detail beyond the schema, so 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 the source (LoopNet), resource (commercial real estate listings) and scope (a US city, for sale or for lease, pages 1-20), and enumerates the returned fields. It does not explicitly differentiate from commercial-oriented siblings like realestate_commercial_real_estate_listings or realestate_showcase_commercial, so it falls short of a 5.

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 implied: commercial listings in a US city, with deal type and page range noted. There is no explicit statement of when to pick this over the other commercial or aggregator siblings, and no exclusions or prerequisites beyond the US-city constraint.

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