imoveis_por_agencia

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

No annotations exist, so the description carries full burden. It does not disclose behavioral traits such as read-only nature, rate limits, or prerequisites. The tool likely performs a read operation, but this is not explicit.

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 concise (one short sentence). It is front-loaded with the core purpose. However, it sacrifices necessary detail, making it less informative.

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 4 parameters (including nested objects) and no output schema, the description is incomplete. It does not explain how to use parameters like filtros or paginacao, nor what the response contains.

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 50% (campos and filtros have descriptions). The tool description does not explain any parameters, failing to add meaning beyond the schema. For example, 'agencia' is required but not described.

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 'Imóveis de uma agência específica' clearly states the tool retrieves properties for a specific agency. It distinguishes from siblings like imoveis_pesquisar (general search) and imoveis_por_corretor (by agent). However, it is minimal and could be more precise.

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 explicit usage guidelines are provided. The description implies use when you need properties from a specific agency, but it does not mention when not to use it or alternatives (e.g., imoveis_pesquisar for broader searches).

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