imapsync_migrations

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'IMAP migration tasks' does not state whether this is a list, create, delete, or status operation, nor does it mention side effects, permissions, or scope. This is essentially missing.

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 short but under-specified rather than concise. It is a fragment that restates the tool name and does not provide enough structure to help an agent invoke the tool correctly.

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?

Even with an output schema present, the description fails to clarify the core action of the tool. The presence of multiple imapsync sibling tools makes the missing verb and scope particularly harmful, so the definition is not complete enough for correct selection and invocation.

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 tool has zero parameters and the schema coverage is 100%, so the schema fully communicates that no arguments are accepted. With zero parameters, the baseline is 4, and the description does not need to add parameter details.

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 'IMAP migration tasks' is essentially a noun-phrase restatement of the tool name and lacks a specific verb or operation. It does not distinguish this tool from the closely related sibling tools imapsync_import, imapsync_export, or imapsync_cancel.

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?

There is no guidance on when to use this tool versus the alternative imapsync_* tools. The description provides no context about what scenario calls for 'tasks' versus import, export, or cancel operations.

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