bulk_archive_messages

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

No annotations are provided, so the description carries the full behavioral burden. It says messages are moved to Archive but omits whether the operation is reversible, permission requirements, partial-failure behavior for invalid ids, and any batch size limits — significant gaps for a bulk mutation tool.

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?

A single front-loaded sentence that puts the action and scope first, with zero filler. Nothing in it repeats structured fields verbatim.

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 bulk mutation tool with no annotations and no output schema, the description is too thin — an agent cannot tell how failures are reported or what happens to a batch with partially invalid ids. The absence of any annotation safety signal leaves the behavioral profile largely undescribed.

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?

There is one parameter with 0% schema description coverage, so the schema says nothing about the argument. The description partially compensates by stating the array accepts 'refs or raw ids', which is genuinely useful identifier-format guidance beyond the schema, but it says nothing about array size limits or empty-list behavior.

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?

States a specific verb (move) and resource (many messages) plus the destination (Archive folder) and the batching intent ('in one call'). It differentiates from the singular sibling archive_message through 'many', though it never names the sibling explicitly.

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?

'in one call' implies this is the batch alternative to archive_message, but the description never states when to prefer the bulk form or whether individual calls are ever appropriate. No exclusions or preconditions are mentioned.

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