wordpress_copy_file

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Copy file') but lacks details on permissions required, whether it overwrites existing files, handles errors, or affects system state. This is a significant gap for a mutation tool, making it only minimally transparent.

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, efficient sentence with no wasted words, clearly front-loading the core action. It's appropriately sized for the tool's simplicity, making it easy to parse without unnecessary elaboration.

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 mutation nature, lack of annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't cover behavioral aspects like side effects, return values, or error handling, leaving critical gaps for an AI agent to operate effectively in a WordPress environment.

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 mentions 'source' and 'destination' implicitly by referring to copying 'to another location', but with 0% schema description coverage, it doesn't add meaningful details beyond the schema's property names. It fails to specify path formats, validation rules, or examples, resulting in a baseline score due to the schema's lack of descriptions.

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 verb ('Copy') and resource ('file') with the scope 'within WordPress', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'wordpress_move_file' or 'wordpress_duplicate_post', which could involve similar file operations, leaving room for improvement in specificity.

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' (which might move instead of copy) or 'wordpress_duplicate_post' (which might copy posts rather than files). There are no explicit instructions on prerequisites, contexts, or exclusions, limiting its utility for an AI agent.

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