write_file

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

With no annotations, the description carries the full burden, and it does disclose the key destructive trait: existing files are overwritten. It says nothing about parent-directory creation, encoding, size limits, or failure behavior on missing paths, which are the remaining risks for a write tool.

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 no filler. It is efficient, though the brevity comes at the cost of the missing detail noted elsewhere rather than being purely a virtue.

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 needn't be explained, but for a two-required-param mutation tool with no annotations and zero schema descriptions, the description leaves path semantics, overwrite side effects on directories, and error conditions unaddressed.

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 0%, so neither parameter is documented anywhere. The description doesn't clarify whether path is absolute or workspace-relative, nor whether content is treated as UTF-8 text or raw bytes — both material to invoking it correctly.

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?

Names a specific verb pair (create/overwrite) and resource (file in the workspace), which is enough to separate it from read_file and list_files. It stops short of explicitly differentiating itself from run_python, which could also write files.

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 versus run_python or other write paths, and no prerequisites stated. The only implied usage cue is the word 'overwrite', which hints at caution but doesn't route the agent anywhere.

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