project.files.write.v1

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states the write action and location but does not disclose whether existing files are overwritten, whether directories are auto-created, whether content is truncated or appended, or any permission/encoding details. For a mutation tool with zero annotation coverage, this is a significant transparency gap.

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, which is efficient in length. However, it is under-specified rather than appropriately concise - it packs minimal information into its one sentence. At this brevity, it's borderline tautological with the tool name 'project.files.write'.

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 mutation tool with no annotations, an output schema exists but the description does not explain what it returns, and several sibling write-related tools (write_project_file, project.files.write.v1) create ambiguity without differentiation. With a simple 2-param tool this could be adequate with good annotations, but with zero annotation coverage the description should disclose overwrite behavior, path handling, and return semantics. It's incomplete for the complexity of a file-write operation.

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%, meaning neither the schema nor the description documents the parameters' meaning. The description mentions 'text file' (implying content is text) and location, but doesn't clarify what 'path' should be (relative or absolute, subdirectory support), or the encoding/format expectations for 'content'. With 0% coverage, the description must compensate but does so only minimally.

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 says "Write text file to WP_PROJECT_ROOT," which identifies a write verb and a resource (files at project root). It's clear this writes a file, but it doesn't explain the write semantics (create vs overwrite, append behavior), and with sibling tools like project.files.read.v1 and project.files.list.v1, only read/list are contrasted implicitly. The purpose is minimally clear but lacks depth about whether existing files are overwritten or if path can point into subdirectories.

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 guidance on when to use this tool versus alternatives. Sibling write_project_file and project.files.write.v1 appear to be near-duplicates, yet the description offers no differentiation. No exclusions, prerequisites, or context for choosing this over write_project_file or content-related tools are given.

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