copy

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It fails to mention critical mutation behaviors: whether copies overwrite existing files, whether folder copies are recursive, preservation of metadata, or conflict resolution strategies.

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?

Single sentence is appropriately sized for a two-parameter tool. The action verb appears first. However, extreme brevity contributes to gaps in behavioral transparency and usage guidelines.

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?

Adequate for basic invocation but incomplete given zero annotations and no output schema. Missing essential context for a mutation tool: success/failure behaviors, idempotency characteristics, and response structure.

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 100% (both parameters have basic descriptions). The description does not add parameter-specific guidance (e.g., path format requirements, absolute vs relative paths) beyond the schema's 'Source path' and 'Destination path' labels. Baseline 3 is appropriate.

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?

States specific verb (copy) and resource (file or folder) with location context (Dropbox). However, it does not explicitly differentiate from the sibling 'move' tool, which performs a similar path-based operation.

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?

Provides no guidance on when to use this tool versus the sibling 'move' tool or other alternatives. No mention of prerequisites such as path existence or permissions.

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