imovel_cadastrar_fotos

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

With no annotations provided, the description carries full responsibility for disclosing behavior, but it fails entirely. It does not mention whether photos are appended or replaced, any size/format constraints, required permissions, or side effects like overwriting existing photos.

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 (one sentence) but does not earn its place—it merely restates the tool's name in verb form. It lacks structure or important details, making it too minimal for effective use.

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 complexity (2 required params, no output schema, no annotations), the description is severely incomplete. It omits return values, behavior, and integration context with sibling tools like 'imovel_alterar' or 'imovel_fotos'.

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%, and the description provides no explanation of the parameters. 'codigo' and 'fotos' remain cryptic; the 'fotos' array of objects has no defined structure. The description adds zero value beyond the raw schema.

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 states the verb 'Adiciona' (adds) and the resource 'fotos ao imóvel' (photos to the property), making the basic purpose understandable. However, it does not explicitly differentiate from the sibling tool 'imovel_fotos' which likely retrieves photos, but the action is distinct enough.

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?

There is no guidance on when to use this tool versus alternatives. No context is provided about prerequisites (e.g., property must exist) or situations where this tool is appropriate. The description offers no 'when to use' or 'when not to use' information.

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