Filesystem inside wp-content

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

Annotations only say openWorldHint and destructiveHint; the description adds genuinely new behavioral context that the annotations do not: writes are jailed to wp-content, extension-limited, and the prior file is backed up under wp-content/woodpresser-backups. That materially lowers the perceived risk of destructive ops. It still omits auth/permission requirements and error behavior.

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?

Two dense sentences: the operation/scope statement first, then the write-safety constraints. No filler, no repetition of the title, and the risk-relevant information is front-loaded.

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 destructive multi-op filesystem tool with no output schema, the description covers the essential safety model (jail, extension limit, backup). Minor gaps remain: nothing about return shapes for read/stat, pagination for list, or the specific allowed-extension policy.

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 coverage is 67%: path and content carry descriptions, while op is only an enum with no prose. The description enumerates the same op values as the enum, so it adds little beyond the schema aside from naming what each operation does at a high level. Baseline 3 is appropriate.

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 names the exact operations (list, read, stat, write, append, mkdir, delete) and the resource/scope ('files under wp-content'), which maps cleanly onto the op enum. It is clear what the tool does, though it does not explicitly contrast itself with the many wp_content_* and wp_media_* siblings that could look similar.

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?

There is no when-to-use or when-not-to-use guidance and no named alternatives, despite a crowded sibling set where wp_content_get, wp_media_upload, and wp_php_run all overlap in the filesystem/content space. The op list implies usage but leaves the agent to infer selection.

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