panelica_file_manager_post_v1_files_copy

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Copy files', giving no information about overwrite behavior, recursion, permissions, or error handling. This is insufficient for a file operation tool.

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?

Extremely concise (two short lines of actual content) but at the expense of missing critical information. It is under-specified rather than efficiently structured.

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 tool's complexity (file copy operation with a nested body parameter and no output schema), the description is severely incomplete. It fails to explain the operation's scope, conflict handling, or return value.

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 no meaning to the parameter. The input schema has one parameter 'source_paths' with an empty description. The description does not explain what source_paths should contain (e.g., list of file paths) or how the copy target is specified (likely missing 'destination_path' parameter?). This is a significant gap.

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 states 'Copy files', which clearly identifies the verb (copy) and resource (files). It is specific but does not distinguish from sibling tools like move or compress. The HTTP path and category provide additional context.

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 move or compress. An agent would not know whether copy or move is appropriate for a given scenario.

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