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

Annotations already declare read-only and open-world behavior, and the description adds substantial context: data comes from the public search page, results are paginated at 30 per page with a total count, and calls cost $0.002 in USDC via x402 with failed calls not charged. These are material behavioral details beyond the annotations.

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?

The description is dense but front-loads the purpose and location scope, then adds return fields, pagination, source, and pricing. It could be split for readability, but little 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 read-only paid search tool with an output schema and complete input schema coverage, the description supplies source, pagination, cost model, and return-field context. An agent has enough information to call it correctly and understand the payment implication.

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 both parameters are already documented. The description reinforces the location format with examples and adds pagination behavior, but it does not add much page-parameter semantics 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 resource and scope: luxury homes for sale on JamesEdition for a country/region/city location. It is distinguishable from generic real-estate siblings by the JamesEdition source, though it does not explicitly name alternatives or when to prefer them.

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 usage context through the location slug format and examples, plus the public-search-page source. It does not say when not to use it or which sibling tool to use for other property types or locations.

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