imoveis_listas

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

No annotations exist, and the description does not disclose any behavioral traits such as whether the operation is read-only, requires authentication, or has side effects. The description is minimal and adds no transparency.

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 description is very short, which is concise, but it is a fragment lacking structure. It could be improved with a full sentence and better organization, though it does not waste 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?

Given the simple schema (one enum parameter) and no output schema, the description is incomplete. It does not specify the return format or fully cover all allowed input values, leaving the agent uncertain about what to expect.

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?

The description lists some enum values ('cidades, bairros, tipos') but omits 'finalidades' and 'categorias'. It does not explain what each option returns or how to use the parameter. With 0% schema description coverage, the description should compensate but only partially does.

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 'Listas de cidades, bairros ou tipos' suggests the tool returns lists, but it uses a noun phrase rather than a clear action verb. It mentions three of the five enum options but omits 'finalidades' and 'categorias', making the purpose partially clear but incomplete.

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?

No guidance is provided on when to use this tool versus alternatives. Among many sibling tools related to properties and clients, there is no indication of context or prerequisites.

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