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

readOnlyHint=true already covers the safety profile, and the description adds genuinely new behavioral detail: the payload includes nested related data (owners, history), and the underlying endpoint is POST /v1/rex/Properties/read. It does not say what happens for an unknown id or whether access is scoped, which keeps it below 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?

Three short clauses with the resource and id provenance front-loaded and the endpoint last. The nested parenthetical listing returned sections is dense but every element carries information; nothing is padded.

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?

With no output schema, the description correctly carries the burden of telling the agent what comes back (address, attributes, features, owners, history) and that the full record is large. Missing only failure/not-found semantics and permission scoping for a read of a single record.

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 the baseline is 3; the description earns an extra point by explaining where the required `id` originates (search or autocomplete), which the schema only calls 'The property id.' The `fields` parameter's large-record tradeoff is already fully documented in 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 verb+resource ('One property by id') and enumerates what the record contains (address, attributes, features, owners, history), which clearly separates it from the search/autocomplete siblings. It stops short of naming the sibling that produces the id, but the singular-by-id framing makes the distinction obvious.

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 id comes from a search or autocomplete' tells the agent the prerequisite step and steers it to the right family of tools before calling this one. No explicit when-not or cost/volume exclusion is given, so it is clear context rather than full routing guidance.

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