copy_message

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description merely restates the copy operation without adding context such as whether the original remains, permission requirements, or return values. It adds no behavioral information beyond the title and name.

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, direct sentence with no filler. However, it may be too terse, omitting important context, but as a statement it is concise.

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 2-parameter tool with no output schema, the description is minimally sufficient but lacks key context such as behavioral difference from move_message, whether the copy preserves metadata/attachments, or what the response contains. Given the sibling tools include move_message, this missing distinction is a notable gap.

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 explain the two required parameters beyond their self-explanatory names (message_id, destination_folder_id). It fails to compensate for the missing schema descriptions, leaving the agent to rely on parameter names alone.

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 uses the verb 'copy' and specifies the resource (message) and target (another folder), making the primary action clear. It distinguishes from 'move_message' implicitly via the term 'copy', but does not explicitly state that the original is retained.

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?

No guidance is provided regarding when to use this tool instead of siblings like move_message. The description lacks any exclusions or alternative recommendations, leaving the agent to infer usage.

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