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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value by disclosing the breadth of returned data (Ofsted grades, broadband, nearby amenities), which tells the agent what one call actually yields. It doesn't mention failure behavior for a stale/invalid home_id.

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 front-loaded sentence that leads with the usage trigger and ends with the parameter. The long enumeration of data categories is dense but each item is informative for selection; it is not padded prose.

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 values need not be explained, yet the description helpfully previews the coverage. With annotations, a full schema, and a clear usage trigger, an agent has what it needs; only error/staleness behavior is absent.

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 the single home_id parameter is already documented as coming from search_homes. 'Takes the home's id' merely restates the schema, adding no syntax, format, or constraint detail beyond it.

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 ('get a home's details') scoped to a single home, and explicitly anchors it to search_homes results, distinguishing it from the plural sibling search_homes and from compare_homes. The enumerated detail categories make the scope unambiguous.

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 a clear trigger ('Use this when the user asks about one home from search_homes results') and implicitly routes discovery to search_homes. It stops short of an explicit when-not or naming compare_homes as the alternative for multi-home questions.

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