wordpress_copy_file

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

With no annotations provided, the description must disclose behavioral traits. It only restates the operation name without addressing potential side effects like overwriting existing files, creating directories, or handling permission errors. This leaves the agent with an incomplete behavioral model.

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, short sentence that is immediately clear and free of filler. It is efficient, though it lacks additional structure or context that would make it more useful.

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 file operation with no annotations, no output schema, and no parameter descriptions, this description is severely under-specified. It does not mention return values, error conditions, path resolution, or overwrite behavior, leaving the agent with insufficient information to invoke the tool confidently.

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 input schema has two parameters (source, destination) with no descriptions, and schema description coverage is 0%. The description does not explain what these parameters represent (e.g., relative paths, URLs, file names) or any expected format, so the agent has no semantic guidance beyond the parameter names.

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 ('file'), and the destination ('another location within WordPress'). This differentiates it from sibling tools like wordpress_move_file (which moves rather than copies) and wordpress_delete_file.

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 such as wordpress_move_file or wordpress_write_file. There is no mention of context, prerequisites, or when a copy would be preferred over a move.

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