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

Annotations already declare read-only and non-destructive intent, lowering the bar. Description adds that results include photo, approximate address, price, and ID, plus the list-return behavior. Does not discuss pagination or response structure, but adds meaningful context beyond 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 sentences, front-loaded with the core action, filters, and return fields. No wasted words.

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 14 parameters, no output schema, and a required natural-language parameter, a short list of filters is insufficient. It does not explain pagination, the role of 'descricao', or the non-residential types allowed in the schema. The description is adequate for a simple filter tool but not for this complexity.

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 79%, but description omits the required 'descricao' parameter entirely and fails to mention other params like finalidade, imobiliaria, limit/offset. Although it lists common filters, it does not clarify that the search is driven by a natural-language description, which is essential. The description also omits enum options beyond casa/apartamento/terreno.

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?

Description clearly states it searches residential real estate listings from partner agencies in Brazil. It lists filters and return fields, distinguishing it from sibling tools like detalhes_imovel (details) by specifying it returns a list with IDs for detail lookup.

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?

Implies usage for property search with filters, but does not explicitly state when to prefer this over sibling tools like imoveis_proximos or comparar_imoveis. No exclusions or alternative recommendations.

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