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

The readOnlyHint annotation covers the safety profile, and with no output schema the description carries the burden of describing the return payload — which it does well by enumerating amenities, description excerpt, cross-site matches, and Domly/photo/contact links. It does not cover failure behavior for an invalid id, so it stops short of a 5.

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?

A single sentence that front-loads the core action ('Details of one rental listing by its id') before enumerating returned contents. Efficient, though the long mid-sentence list of return items slightly dilutes scanability.

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 two-parameter read tool with no output schema, the description is largely self-sufficient: it names the identifying source and sketches the response contents. Minor gaps remain around error behavior on a bad id and the role of the language parameter, but nothing critical is missing for correct invocation.

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 (id, language enum) are already fully documented in the schema. The description's 'by its id from search_listings' merely echoes the id description and adds no syntax or format detail beyond it; 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 (get/details), a precise resource (one rental listing), and the identifying key (its id from search_listings). An agent can immediately distinguish this single-listing fetch from the sibling search_listings list operation.

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 rather than stated: 'by its id from search_listings' suggests calling this after a search to drill into one result. There is no explicit when-to-use/when-not guidance and no mention of the other siblings (get_price_stats, request_realtor), so the routing signal is only implicit.

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