imovel_deletar_video

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

The description indicates the operation is permanent ('permanentemente'), which implies destructive behavior. However, no annotations are provided to fill gaps, and the description lacks details on side effects, authorization needs, or whether the action is reversible.

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 sentence that efficiently conveys the core functionality with no wasted words.

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?

While the description fully states the purpose, it does not mention return values (no output schema) or any confirmation of success. For a destructive tool, additional context about what happens after execution would be beneficial but not essential.

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 100%, so the baseline is 3. The tool description adds no additional meaning beyond what is already documented in the input schema for the two parameters.

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 action: 'Remove permanentemente um vídeo de um imóvel' (permanently remove a video from a property). It specifies a specific verb and resource, and distinguishes from sibling tools which cover other operations like adding or altering imovel data.

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, nor any prerequisites or conditions. The description does not mention when not to use it or any related tools.

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