Arquivar vários emails

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

Annotations already indicate destructiveHint=false, but the description adds useful behavioral context: emails remain available after archiving and leave the Inbox. It also discloses the required user-communication step, which is not inferable from annotations or schema.

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 compact and front-loaded with the action and limit. The quoted example in the second sentence is slightly redundant but earns its place by specifying exactly what the agent must say before executing.

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 single-parameter batch operation with no output schema, the description covers the action, batch limit, non-destructive nature, and a required pre-execution message. It is sufficient for correct invocation, though it does not mention connection or account prerequisites.

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% since the ids parameter is described as 'IDs dos emails. Máximo 50.' The description mostly restates the batch size and does not add new parameter-level meaning such as ID format, source requirement, or how to obtain valid IDs.

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 states a specific verb and resource: 'Move vários emails para o Arquivo Morto de uma vez (até 50).' It clearly scopes the operation as batch archiving and explicitly distinguishes it from deletion, which also separates it from the singular sibling tool outlook_arquivar_email.

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?

The description provides a clear usage instruction: 'Antes de executar, informe a quantidade,' and clarifies this is archival, not deletion. However, it does not explicitly name alternatives or give exclusion criteria such as when to use outlook_mover_emails or outlook_arquivar_email instead.

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