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

Beyond the readOnly and openWorld annotations, the description discloses important behavior: it reads embedded JSON because no official API exists, returns only the first results page, and charges $0.002 USDC per successful call while failed calls are not charged. These are material operational details an agent needs before invoking it.

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 front-loaded with purpose and scope, followed by the technically important source and payment details. Every sentence contributes useful information without repetition or 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?

For a one-parameter, read-only scraping tool with an output schema, the description supplies the key context: source site, geography, first-page limitation, returned fields, embedded-JSON basis, lack of official API, and payment terms. No important invocation detail 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 description coverage is 100%, and the single limit parameter is fully described in the schema. The description reinforces the limited first-page scope but does not add parameter-level details beyond what the schema already provides, 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?

The description states a specific verb and resource: Dublin homes for sale from the myhome.ie search page. It also enumerates returned fields and clearly ties the tool to a unique source, distinguishing it from sibling real-estate tools tied to other sites or regions.

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 Dublin/myhome.ie context implies when the tool is appropriate, but there is no explicit guidance on when to choose it over alternatives such as rightmove_property, zoopla, or other Irish property sources. No exclusions or alternative-routing advice are provided.

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