move_by_search

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

The description discloses the dry-run default, the consent workflow, the rejection of unfiltered calls, the max_messages default and cap, the folder scan behavior, and matching semantics for from_address and date inclusivity. This goes well beyond the annotations, which only indicate mutability, adding critical context for safe execution.

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 well-structured with a concise summary, safety note, and an Args list. Every sentence adds value; the dry-run explanation is repeated in both the intro and the Args list, but that's acceptable given its importance. The layout is front-loaded with the core purpose and then safety details.

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 the 9 parameters and the output schema, the description covers all operational behaviors and constraints. The safety workflow and parameter semantics are fully specified, making the tool self-sufficient for correct invocation. Nothing essential is left to guess.

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's Args section provides all parameter semantics. Each parameter is explained with concrete examples (e.g., dest folder names, date format, matching rules), adding significant value beyond the schema's bare types and defaults.

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 clearly states the tool moves emails matching conditions in bulk, and explicitly frames it as 'move_messages の大量版' (large-scale version of move_messages), distinguishing it from the sibling tool. The verb 'move' and the resource 'emails matching conditions' are specific and unambiguous.

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 explicit usage guidance: use dry_run first, show the count, get consent, then re-invoke with dry_run=False. It also states that calls without any filter conditions are rejected, preventing misuse. The 'large-scale version' implies when to use over move_messages, and the safety protocol is clearly outlined.

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