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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorld=false, so the safety profile is fully covered by structured data. The description adds the useful link that the id must come from search_homes, but says nothing about latency, rate limits, or error behavior for a missing id; with an output schema present, further behavioral detail is largely unnecessary.

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?

One sentence, front-loaded with the triggering condition followed by the returned-field list. It is dense but every clause maps to a real capability; the long enumeration is the only slight strain on readability.

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 a rich annotation set and an output schema, the description is complete enough for correct invocation — it identifies the trigger, the required input, and the source of that input. The field enumeration partially duplicates what the output schema presumably documents, but nothing an agent needs is missing.

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% for the single home_id parameter and the schema already says 'The id from search_homes.' The description repeats that constraint ('Takes the home's id') without adding format or validity details, so it lands at the baseline for a well-documented single-parameter 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 and resource and enumerates the exact fields returned (advert, rooms, tenure, EPC, schools, etc.), which is far more informative than the title. It also anchors the tool relative to search_homes results, so an agent can distinguish it from siblings without opening a schema.

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?

Gives explicit usage context: 'Use this when the user asks about one home from search_homes results,' which cleanly separates it from the bulk search case. It does not name when-not to use it or explicitly route to compare_homes/get_area_guide, so it falls one step short of full guidance.

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