document_copy_operation

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

The description lacks behavioral details beyond the basic 'copy' action. No annotations are present to clarify side effects (e.g., whether the target is overwritten if it exists, whether the source remains unchanged, or any permission requirements). The description does not mitigate the absence of annotations.

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, clear sentence with no unnecessary words. It efficiently conveys the core functionality without redundancy.

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?

Given the lack of an output schema and the presence of 5 required parameters, a more detailed description is needed. Important context such as what happens to an existing target operation, whether copying is recursive for sub-resources, and any validation behavior is missing. The description is insufficient for an agent to invoke the tool correctly without additional knowledge.

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 coverage is 100%, meaning all parameters (session, sourcePath, sourceMethod, targetPath, targetMethod) are described in the input schema. The description adds no additional meaning beyond what the schema already provides, which meets the baseline expectation.

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 ('Copy'), the resource ('an operation'), and the context ('from one path/method to another'). It effectively distinguishes from sibling tools like 'document_move_operation' (which moves instead of copies) and 'document_add_operation' (which adds a new operation rather than copying an existing one).

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 on when to use this tool versus alternatives such as 'document_move_operation' or 'document_add_operation'. There are no prerequisites, constraints, or scenarios mentioned that would help the agent decide between copying, moving, or adding an operation.

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