move_emails

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

With no annotations, the description must carry behavioral disclosure. It adds useful context that UIDs are permanent identifiers and points to list_folders, but it does not mention side effects like source folder behavior, reversibility, or error cases. This is moderate but not comprehensive.

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 two concise sentences. The first states the core action and parameters; the second provides crucial context about UIDs and a practical usage tip. Every word earns its place, with no redundant content.

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 tool with three simple parameters, no output schema, and no annotations, the description covers the essential action, key parameter semantics, and a prerequisite tool. It does not fully describe error conditions or return behavior, but it is adequate for the tool's apparent simplicity.

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?

The input schema already covers all parameters with descriptions (100% coverage). The description adds value by explaining that UIDs are permanent identifiers, which is not in the schema, and reinforces the use of list_folders for folderName. This goes beyond the baseline schema coverage.

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's action: 'Move emails to a specified folder using UIDs.' It distinguishes from sibling tools like delete_emails or archive_emails by specifying the move operation. Mentioning UIDs and list_folders further pins down the resource and prerequisites.

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 hint: 'Use list_folders to see available folders,' which guides the agent on a necessary precursor step. It does not explicitly mention alternatives or when not to use this tool, but the context of permanent UIDs and folder listing gives practical usage guidance.

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