copy_document

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

The description discloses that the active session and source path are unchanged, and that the output path must end in .docx. However, it does not mention overwrite behavior, authorization needs, or file size constraints. As no annotations are provided, the description carries the full burden for behavioral transparency.

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 five sentences that are front-loaded (core purpose first), clear, and free of unnecessary information. Every sentence adds value.

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 simple tool with one parameter and an output schema (implied by the return description), the description covers the essential aspects: purpose, effect on session, parameter constraint, and return value. However, it is missing information about whether the tool overwrites existing files, which would be important for an agent.

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 adds significant value to the single parameter 'output_path' by specifying it must end in .docx, which is not present in the schema (0% coverage). It also describes the return format, providing context beyond the schema.

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 purpose: 'Save a complete snapshot of the open document to a new path.' It specifies the verb (save), the resource (open document), and the outcome (snapshot to new path). It distinguishes from siblings like 'save_document' by emphasizing copying to a new path without altering the active session.

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?

The description implies usage for creating a copy at a new path, but does not explicitly state when to use this tool versus alternatives (e.g., 'save_document', 'convert_to_pdf'). No exclusions or prerequisites are mentioned.

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