imovel_cadastrar_documentos

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

With no annotations available, the description carries full burden for behavioral disclosure. It only states 'add documents' without any details on whether documents are appended or replaced, what types are supported, size limits, or side effects. This is insufficient for an AI agent to understand implications.

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 concise (one short sentence) but this comes at the cost of omitting critical information. It is not structured with front-loaded key details; rather, it is an underspecified statement that fails to earn its 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?

Given the tool has a parameter requiring an array of objects (without defined structure in the schema) and no output schema, the description is profoundly incomplete. It does not explain what constitutes a valid document object, error conditions, or how the property is identified. The complexity demands much more context.

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 input schema has two parameters ('codigo' and 'documentos') with 0% schema description coverage. The description does not explain what 'codigo' represents (e.g., property code) or the expected structure of objects in the 'documentos' array. No additional meaning is provided beyond the schema field names.

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 clearly indicates the tool's purpose: adding documents to a property ('Adiciona documentos ao imóvel'). It uses a verb+resource pattern and is easily understood. However, it does not differentiate from sibling tools like 'imovel_anexos' which might have similar functionality.

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. There is no mention of prerequisites, context, or exclusions. The description lacks any usage direction.

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