copy_document

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

The description explicitly states that 'The active session and source path are unchanged,' which is important behavioral context for a copy operation. With no annotations provided, the description carries the full burden and does well by clarifying side effects. However, it does not mention permission requirements or any potential limitations.

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 (4 sentences) and front-loaded with the main purpose. The structure clearly separates the action, side effects, and parameter details. No unnecessary information.

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 copy tool, the description covers the core behavior, side effects, and output format. Given that an output schema exists (indicated in context), the description does not need to detail return values. All essential information is present.

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 schema has 0% description coverage for parameters, but the description adds a constraint that output_path 'must end in .docx.' This is helpful but does not fully compensate for the missing schema descriptions. The return format is also specified, adding value.

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 clearly states the tool's action: 'Save a complete snapshot of the open document to a new path.' The verb 'save snapshot' is specific, and the resource 'open document' is unambiguous. Among siblings, there is no other copy tool, so it stands out.

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 on when to use this tool versus alternatives like save_document. The description does not mention prerequisites, exclusions, or scenarios where a different tool would be appropriate.

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