Write File

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

The annotations set destructiveHint=false, but the description describes an overwrite operation, which is inherently destructive. This contradiction undermines transparency. The description adds no clarifying behavioral context beyond the annotations.

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 two sentences, efficiently conveying the tool's core purpose and a key usage guideline. No unnecessary words.

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?

The description covers the basic operation but omits details about encoding, size limits, behavior when file exists, or binary file handling. Given the tool has an output schema (presumably documenting returns), it partially compensates but still feels incomplete for nuanced scenarios.

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?

With 0% schema description coverage, the description should compensate but only offers minimal context. It mentions 'text file' to hint at content type but does not explain the meaning of parameters like projectPath, file, content, or createDirs.

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 tool creates or overwrites a text file inside a project. The verb 'Create or overwrite' combined with the resource 'text file' precisely defines the action, and it distinguishes itself from sibling tools like file.delete, file.copy, etc.

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 advises 'Use code.read first when modifying an existing file,' which provides guidance on when to read before writing. However, it doesn't explicitly state when not to use this tool or suggest alternatives for non-text files.

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