Mover arquivo ou pasta

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

Beyond the annotations (readOnly=false, destructive=false), the description exposes the default conflict error behavior, the rename strategy with an example, the non-destructive nature of the move, and the requirement to keep operations within authorized folders. It also instructs the agent not to decide conflicts autonomously.

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 front-loaded with the core operation and constraint, then details conflict behavior and user interaction. The included user-facing script example is useful but makes it slightly longer than strictly necessary.

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?

For a mutation tool with no output schema, the description covers operation, constraints, conflict handling, and required user communication. It doesn't specify the return format or error behavior for unauthorized paths, but those are not critical for an agent to invoke it correctly.

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 covers all three parameters, so baseline is 3. The description adds value by explaining the default conflict behavior and illustrating the 'rename' strategy with 'arquivo (2).pdf', which is not in the 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 uses a specific verb ('Move') and resource ('arquivo ou pasta'), and clarifies the scope ('sempre dentro de pastas autorizadas'). It is clearly distinct from siblings like copiar_item or renomear_item, though it does not explicitly name them.

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?

Provides clear pre-call and post-call guidance: explain to the user what will be moved, where it will go, that the file will persist, and confirm after moving. It also instructs the agent to ask the user on name conflicts. However, it does not explicitly state when to prefer this tool over copiar_item or renomear_item.

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