Mail Move Message

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

The description provides no behavioral details about side effects, reversibility, permission requirements, or what happens to the source mailbox. The annotations are sparse and the description adds no contextual value beyond them, nor does it explain the 'delegated' nature.

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 this is under-specification, not concise value. The single sentence spends its words restating the tool name and platform wrapper, so it does not earn its place.

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 mail operation with an output schema and multiple contextually significant parameters, the description is essentially empty. It fails to mention the operation, target semantics, source behavior, or any conditions for use.

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%, and the description does not compensate at all. It does not explain message_id, target_account, or target_mailbox semantics, cross-account moving, or the meaning of optional versus required parameters.

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 only restates the tool name and its category ('Delegated Apple domain tool') without stating what it does. There is no verb+resource relationship, no mention of moving a message, and no distinction from mail_archive_thread or mail_mark_message.

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 alternatives. Nothing explains the difference between moving a message, archiving it, deleting it, or marking it, despite many mail-related siblings existing.

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