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

With no annotations provided, the description carries the full burden and does disclose meaningful behavior: it is a logged-out (unauthenticated, read-only) call, it only resolves rights-cleared published homes, and it returns a save link among other fields. It stops short of describing error shape or what happens for an unpublished or non-existent id beyond implying non-resolution.

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 fragments, front-loaded with the resource and payload, with no padding. The telegraphic style ("Logged-out.") is efficient but slightly clipped, and the field list could be tied more clearly to return values.

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 single-parameter lookup with no output schema, the description compensates well by enumerating the returned fields and stating the visibility gate. A note on failure behavior for invalid or unpublished ids would make it fully complete.

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% and the single property_id parameter is already documented with type, minimum, and the /homes/slug-1 example, so the schema does the heavy lifting. The description adds no additional meaning about the id beyond what is structured, so 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?

"Full public detail for one home" states a specific resource (home), scope (single, full public detail), and enumerates the payload (price, land, source, evidence, save link). It implicitly contrasts with the sibling search_homes but never names it, so an agent must infer the single-vs-list distinction.

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?

"Only rights-cleared published homes resolve" is a useful precondition that tells the agent when this call will fail, and "Logged-out" signals no auth is required. However, there is no explicit guidance on choosing this over search_homes or board_save, and no mention of how to obtain a valid property_id first.

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