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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful behavioral context by enumerating the breadth of returned data, including photo-detected features, fact-grounded description, video tour presence, similar homes, and source listing link.

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?

The purpose and input are front-loaded, and every listed data field earns its place by clarifying scope. It is a single long sentence, which is slightly unwieldy, but not padded with irrelevant material.

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 annotations covering safety and an output schema documenting the return shape, the description supplies all an agent needs to select and invoke the tool correctly. It also names the input format and provenance explicitly.

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 100% and already documents the single 'home' parameter as an enzos.ai URL or 16-character id. The description restates the same format and adds only that the id is 'as returned by search_homes', so it does not meaningfully exceed 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 the specific verb 'Get' and resource 'full facts for one for-sale home on Enzo's', then enumerates the exact data included. This clearly distinguishes it from search_homes, which returns multiple homes.

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?

Explains that the input is an Enzo's home URL or id 'as returned by search_homes', which makes the intended workflow clear. It does not explicitly exclude alternatives like home_verdict or below_market_deals, but the usage context is clear.

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