copy-mail-message

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

Description notes the return of a newly created message with a new ID, adding behavioral context. With annotations indicating destructiveHint=true, the description does not contradict but could further clarify that the original message remains unchanged.

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 concise with two sentences and a tip, directly providing necessary information without extraneous 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?

The description covers the core parameter and return value but does not mention the optional 'includeHeaders' and 'excludeResponse' parameters, which are described in the schema. Overall, it is adequate for the tool's complexity.

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 description explains the DestinationId parameter with examples (inbox, archive, junkemail), which is missing from the schema. It thus adds significant meaning beyond the schema's 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?

Description clearly states the verb 'copy' on resource 'message' to a target 'folder', and distinguishes from the sibling 'move-mail-message' by explicitly mentioning moving as an alternative.

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?

Explicitly directs users to 'move-mail-message' for moving instead of copying, providing a clear alternative. However, it does not elaborate on when one should prefer copying over moving.

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