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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety bar is covered. The description adds genuine domain context beyond that: only approved listings are visible, missing/withdrawn homes return nothing, and the payload excludes private guides, live prices, and any booking authority.

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?

Two sentences, front-loaded with the core action and followed by compact scope exclusions. No filler, though the exclusion list is dense enough to warrant a slightly tighter phrasing.

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 need not be described, and annotations carry the safety profile. The description covers data-scope limitations well; the remaining gap is the undocumented id format and locale behavior, which leaves an agent guessing about identifier semantics.

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 0% and neither parameter is documented in the schema beyond type and constraints. The phrase 'a specific home' only loosely implies id is a home identifier, and locale (with its en/es enum and default) is never explained in the description, so the coverage gap is largely uncompensated.

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 (Read) and resource (current approved details for a specific home), which distinguishes a single-entity lookup from siblings like search_properties and render_properties. It stops short of explicitly naming the sibling it competes with, so differentiation is inferred rather than stated.

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: you call this when you need details for one already-known home. The negative condition ('Missing or withdrawn homes are unavailable') gives useful scope, but there is no explicit when-to-use-this-vs-search_properties routing and no prerequisites mentioned.

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