copy_document

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

With no annotations, the description must fully disclose behavior but only states 'Create a copy'. It does not mention whether the original document is modified, whether the copy overwrites existing files, or any side effects. This lack of transparency hinders safe tool selection.

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 short and to the point, but it sacrifices detail for brevity. While it avoids verbosity, it is too sparse to fully inform the agent, making it average in this dimension.

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?

Despite having an output schema, the description lacks crucial context such as behavior on existing file, permissions needed, or relationship to the open document state. For a simple operation, it misses key completeness factors.

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 only restates 'dest_path: Destination file path' without adding meaning beyond the schema (e.g., path format, whether it can be absolute/relative, or restrictions). The parameter semantics are insufficient for correct invocation.

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 action ('Create a copy') and the resource ('current document'), making the tool's purpose easy to understand. It is distinct from sibling tools like 'save_document' or 'insert_document', though it could be more explicit about the scope (e.g., 'of the currently open document').

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 provides no guidance on when to use this tool versus alternatives. Sibling tools include various document operations but no comparison or conditions are given, leaving the agent to infer usage context.

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