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

Annotations already declare destructive=true and readOnly=false. The description adds important behavior beyond annotations: future is true by default, creates a per-sender rule that continues applying to new mail, and requires permission to change rules.

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 main action is front-loaded, followed by behavior and parameter sourcing; every sentence adds useful information. It is somewhat dense and uses terse lowercase parameter names, slightly reducing readability.

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 destructive bulk mutation, it covers the scope of affected conversations, destination choices, the default rule-creation behavior, and the permission required for that side effect. It does not describe return values or partial-failure behavior, and there is no output schema to fill that gap.

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%, so the description must carry parameter meaning; it does by explaining destination values (archive, Bin, label), labelId's source, ids' source, and future's default and side effect. It omits details like the 100-id maximum and explicit labelId conditional requirement for destination=label.

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 every conversation from several senders to archive, Bin, or a label. The bulk scope ('several senders', 'every conversation') and the UI analogy to the Subscriptions page clearly distinguish it from the singular moveSubscription sibling.

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?

It gives clear usage context: this is the bulk equivalent of selecting subscriptions in the UI, with ids sourced from listSubscriptions and labelId from getUserLabels. It does not explicitly contrast with moveSubscription or state when-not to use it, so it falls short of full alternative guidance.

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