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

With no annotations, the description carries the full burden. It discloses useful traits: read-only ('details'), no auth implied ('public'), and that results are 'full' rather than a search summary. It says nothing about behavior on invalid/unknown ids, pagination, or errors.

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 with zero filler, front-loaded with the resource and scope, and the id provenance tucked into a brief parenthetical.

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 simple one-parameter read tool with no output schema, the description covers what is returned ('full public details') and where the input comes from. Only failure behavior for a bad id is absent, a minor gap at this complexity level.

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 0% — the lone 'id' parameter is a bare integer with no description. The description partially compensates by identifying the id as a listing id obtained from search_properties, but adds no format or validity details beyond that provenance.

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), resource (one RealEVR Estates listing), and scope ('full public details ... by id'). The parenthetical naming search_properties makes its role distinct from that sibling's search behavior.

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?

'(from search_properties)' implies the id originates from a prior search, giving implied workflow context. However, there is no explicit when-to-use/when-not statement or mention of alternatives such as real_estate_knowledge for non-listing info.

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