email_move

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

With no annotations, the description carries full burden. It states 'move' which implies mutating state, but does not disclose consequences (e.g., what happens if destination folder doesn't exist, whether the operation is atomic, or if there are size limits). The description is too minimal for a mutating operation.

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 a single sentence with no fluff. It directly conveys the core function. It is appropriately concise for a straightforward operation.

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 lack of output schema and annotations, the description is too sparse. It does not inform about success indicators, error conditions, or any constraints (e.g., moving within same mailbox?). For a 3-param tool, more detail is needed to ensure correct usage.

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%. The description adds meaning by explaining 'uids' as email identifiers and 'from'/'to' as folders. However, it does not mention the default value for 'from' (INBOX) or that 'to' is required. The parameter roles are partially clarified.

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 action (move), resource (email UIDs), and the concept of between folders. It distinguishes from siblings like email_delete and email_list. However, it does not mention the default 'from' folder (INBOX), which is useful contextual info.

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 implies usage when you need to relocate emails, but provides no explicit guidance on when to use vs alternatives (e.g., no copy tool is present). It lacks when-not scenarios or prerequisites like required permissions.

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