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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the sort order ('newest first'), that a total live listing count is returned, and a critical operational trait: a per-call price of $0.002 USDC via x402 (Base, Solana, Arc) with failed calls not charged. Payment/auth requirements are exactly the kind of context annotations cannot convey.

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?

One dense paragraph that front-loads the data returned, then filters, then the total count and pricing. The long field enumeration is somewhat list-heavy but each item helps an agent judge fit; little genuine waste.

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?

An output schema exists, so return-shape explanation is not required, and the description still flags the total-count field. Coverage of area slug format and payment model is adequate; pagination behavior beyond the schema's limit param is the only minor omission.

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 all six parameters are already documented. The description restates the filter set (max rent, min bedrooms, furnished, pets) but adds no format or edge-case detail beyond 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?

The description states a specific verb and resource ('UK rental listings from OpenRent (landlord-direct) for a city or area') and enumerates the returned fields, so an agent can tell it apart from sibling UK property tools like realestate_zoopla or realestate_rightmove_property without opening the schema.

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?

It gives useful invocation context ('Filter by max rent, min bedrooms, furnished or pets; newest first'), but never states when to use this source versus the many sibling rental tools (zoopla, rightmove, hotpads_rentals) or any exclusions/limitations.

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