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

Annotations already cover read-only, non-destructive, and idempotent behavior. The description adds meaningful selection context by specifying that only reviewed neighbourhoods are returned, and it exposes the relationship to search_homes.neighbourhoods. This is useful beyond the structured annotations.

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 short sentences with no filler: the first states the action and scope, the second gives an immediate cross-tool usage hint. The most important information is front-loaded.

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 one-parameter list tool, the description is nearly complete: it states what is listed, the scoping market, and how the output relates to search_homes. It does not explicitly describe the response shape, but the presence of ids/names is implied by the search_homes reference.

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%, so the description should compensate. "Inside one market" clarifies that the market parameter selects the containing market, but it does not describe the enum values or expected format. The single-parameter schema and self-explanatory enum limit the gap, making this minimally adequate.

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?

The description uses a specific verb and object: "List reviewed neighbourhoods (barrios/localidades) inside one market." It clearly scopes the tool to neighbourhood-level data for a single market, which differentiates it from sibling tools like get_home, list_markets, and search_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?

The description gives clear usage context: call this to get reviewed neighbourhoods for a market and use the resulting ids/names in search_homes.neighbourhoods. It does not explicitly state when not to use it or compare it to an alternative, but the integration hint is concrete and useful.

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