outlook_copy_message

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

Discloses core behavior: duplicates and source unchanged. No annotations provided, so description carries burden; could mention error cases or permissions, but sufficient for simple copy.

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?

Two sentences, front-loaded with purpose, then usage guideline. No extraneous text.

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?

Covers key aspects for a simple 2-param tool with no output schema. Could mention expected behavior if folder not found, but overall complete.

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 has 0% description coverage; description adds meaning for folder parameter (accepted formats), but none for message_id. Partially compensates.

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?

Clearly states 'Copy a message to another folder (duplicates; source is unchanged).' Specific verb and resource, distinguishes from move sibling.

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 says when to use copy vs move, and gives guidance on folder parameter format: 'folder accepts display names, well-known names, or Graph IDs — prefer names.'

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