write_file

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

The destructiveHint annotation already declares this is a destructive operation, so the description is not carrying the safety burden alone. It does add value by noting the operation overwrites existing content and by defining path resolution (PROJECT_MCP_ROOT or cwd), but omits whether parent directories are created, encoding handling, and any permission requirements.

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?

A single front-loaded sentence with zero filler; the verb, resource, and path-resolution caveat all earn their place.

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?

An output schema exists, so return values need not be explained, and the destructive annotation covers the safety profile. What remains missing is sibling differentiation from edit_file and side effects like parent-directory creation or partial-write failure behavior for a mutation tool.

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%, so the description must compensate for both parameters. It usefully clarifies the path parameter's resolution rules but says nothing about content (encoding, whether it is raw text or a stringified payload), leaving one of two parameters undocumented in both schema and description.

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?

States a specific verb (write/overwrite) and resource (file at path), which is unambiguous on its own. However, it does not distinguish itself from the sibling edit_file, which is the key routing decision an agent faces for this resource.

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?

No when-to-use guidance is given, and no alternative is named. The choice between write_file and edit_file is left entirely to inference, even though 'overwrite' hints at full replacement behavior without saying when that is preferable.

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