imovel_anexos

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

With no annotations and only a minimal description, there is no disclosure of behavioral traits such as whether the operation is read-only, requires authentication, or what happens on invalid input. The description does not add any safety or side-effect context.

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 a single short phrase, making it concise but underspecified. It avoids tautology by adding 'documentos anexos' beyond the tool name, but it lacks necessary structural elements like an action verb or clear context.

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 simplicity of the tool (one parameter, no output schema), the description is incomplete. It does not specify what the tool returns (e.g., list of document references, URLs), how many, or any ordering. An agent would have to guess the behavior, increasing misuse risk.

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 required parameter 'codigo' has 0% schema coverage and is not explained in the description. The description does not clarify what 'codigo' represents (e.g., property ID), nor does it provide format or constraints. The description fails to compensate for the lack of schema documentation.

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 'Documentos anexos do imóvel' (attached documents of the property) indicates the tool relates to property documents, but it is a noun phrase rather than a verb-resource statement. It does not explicitly state whether the tool retrieves, lists, or manipulates these documents. It distinguishes from siblings like imovel_fotos by topic, but the action is implied.

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, typical scenarios, or exclusions. Sibling tools exist for registering documents (imovel_cadastrar_documentos) and other property operations, but the description offers no comparison.

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