move_matching

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

With no annotations provided, the description carries the full burden and does so excellently. It discloses the safety guard (required filter), performance differences (fast native bulk move vs. slower per-message), return value (number of messages moved), and potential long runtime on large mailboxes.

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 information-dense and front-loaded with the primary purpose. Every sentence provides necessary context—safety, prerequisites, performance, and return value—without filler or redundancy.

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?

Given no output schema and complex multi-parameter behavior, the description covers all essential context: required filters, destination existence, limit semantics, return count, and performance caveats. It is complete for an agent to invoke the tool 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 description coverage is 100%, with each parameter already having detailed descriptions. The tool description reinforces key semantics (like limit behavior and from_filter matching) but does not add significant new meaning beyond the schema, so baseline 3 is appropriate.

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 explicitly states the tool's function: bulk-moving every email matching given criteria from a source mailbox to a destination in one pass. This clearly distinguishes it from siblings like move_email or archive_email by emphasizing the bulk, criteria-based nature.

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 explicit usage guidance: one call per substring, requiring at least one filter, creating the destination folder first if needed, and explaining when to omit vs. set the limit. This tells the agent exactly how and when to use the tool, including important prerequisites and trade-offs.

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