wordpress_write_file

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

Without annotations, the description must convey behavioral traits. It mentions 'security validation' and 'optional backup' but does not specify what security validation entails, how backups are created or restored, or whether the tool overwrites existing files. This leaves significant ambiguity.

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 sentence, which is concise and front-loads the action. However, it could be slightly more structured to separate the action from the security and backup features. Still, it is effective.

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?

No output schema is provided, and the tool is complex with security and backup implications. The description does not mention return values, error conditions, or the effect of the backup parameter on behavior. Given the tool's importance, this omission makes it incomplete.

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 0% description coverage, and the description only indirectly references 'createBackup' via 'optional backup'. It fails to explain the format, constraints, or purpose of 'path' and 'content', leaving the agent to infer from parameter names alone.

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 ('Write or create') and the resource ('file'), with specific qualifiers ('security validation and optional backup') that differentiate it from sibling tools like read, copy, or 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_write_plugin_file or wordpress_write_theme_file, nor does it explain the intended use cases or prerequisites for backup or security validation.

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