imovel_informacoes

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

With no annotations, the description carries full burden, but it only states 'summarized/highlighted information' without disclosing read-only behavior, data returned, or any side effects. It is insufficient for an agent to understand expected outcomes.

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 extremely short, but it sacrifices useful detail. It is under-specified rather than appropriately concise, as it omits critical information needed for correct usage.

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 single parameter, no output schema, and no annotations, the description fails to complete the picture. It does not clarify what 'resumidas' means or how this tool differs from 'imovel_detalhes', making it inadequate for effective agent use.

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%. The parameter 'codigo' is not described in the schema or the tool description, leaving its meaning and format entirely undocumented. The description adds no value beyond the name.

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 'Informações resumidas/destacadas' is vague and lacks a specific verb-resource pair. It does not clearly indicate that the tool retrieves a summary of property information, nor does it differentiate from sibling tool 'imovel_detalhes' which likely provides full details.

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 like 'imovel_detalhes' or other property-related tools. The description offers no context for selection.

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