imapsync_import

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

With no annotations, the description carries the full behavioral burden and does add one genuinely valuable disclosure: 'Passwords in the payload are redacted in logs,' plus the confirmation requirement. However, it never discloses that this is a state-mutating import, whether the operation runs synchronously (relevant given imapsync_migrations exists), or how existing mailbox contents are affected.

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 compact and front-loaded: one action sentence followed by a terse args list with no wasted words. The only structural flaw is the ambiguous and potentially misleading 'confirm: Required' statement, which undercuts the otherwise clean format.

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 mutating, cross-system operation with zero annotations and a fully opaque payload object (additionalProperties: true), the description leaves too much unstated: the meaning of 'dest,' whether the operation is asynchronous and tracked via imapsync_migrations, and what happens to pre-existing mail. The redaction note is a good start, but an agent still lacks enough to safely invoke and monitor this operation.

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 must compensate — and it partially does by expanding payload to '(host, user, password, dest)' and flagging confirm, adding real meaning to otherwise opaque structured fields. But the claim 'confirm: Required' conflicts with the schema, which lists only payload as required, and no format or validation details for the payload fields are provided.

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 states a specific action — 'Import mail from a remote IMAP server into this box' — naming the verb, source, and destination in one clear sentence. This makes the tool's basic function unambiguous, and the import direction inherently distinguishes it from siblings like imapsync_export. However, it never explicitly names its sibling alternatives, so differentiation is implicit rather than stated.

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 offers no guidance on when to choose this tool over imapsync_export, imapsync_cancel, or imapsync_migrations, and no prerequisites (e.g., remote server reachability) or decision rules are given. The 'confirm' mention is a parameter note, not a usage condition.

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