imovel_cadastrar

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

Without annotations, the description carries the full burden of behavioral disclosure. It only states 'register a new property' with no information on side effects, idempotency, authentication requirements, or what happens on duplicate entries.

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?

Although only one sentence long, it is too concise to be useful. Essential information about parameters and behavior is omitted, sacrificing clarity for brevity.

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?

The description fails to compensate for the lack of output schema and the complex nested object parameter. Crucial details about the structure of 'dados' and expected return values are missing, making the tool nearly unusable for an agent.

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 sole parameter 'dados' is an object with no defined properties and schema description coverage at 0%. The description provides zero explanation of what fields or structure are expected, leaving the agent blind.

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 'Cadastra um novo imóvel' clearly states the verb (register) and resource (property), distinguishing it from siblings like 'imovel_alterar' (modify) and 'imovel_detalhes' (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 such as 'imovel_alterar' or 'imovel_cadastrar_documentos'. The agent receives no contextual cues for tool selection.

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