wordpress_write_plugin_file

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

With no annotations provided, the description carries full burden. It only discloses automatic backup creation but omits critical behaviors such as whether files are overwritten or created, permissions required, file size limits, or what happens on failure.

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 conveying key purpose and a notable behavior, with no extraneous words. It is optimally concise.

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 absence of output schema, annotations, and schema descriptions, the description is too brief. For a file write operation, it should detail overwrite behavior, supported file types, and error scenarios to be complete.

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 0%, and the description adds minimal semantics beyond parameter names. It does not explain what 'plugin' refers to (slug vs name), whether 'filePath' is relative or absolute, or expected content format.

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 'Write or modify a file in a plugin', specifying the action and resource, and mentions automatic backup, which distinguishes it from generic file write tools like wordpress_write_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 implies usage when writing plugin files and notes automatic backup as a benefit, but lacks explicit guidance on when to use this tool over alternatives like wordpress_write_file or wordpress_write_theme_file, nor does it mention prerequisites or exclusions.

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