write_text_file

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

With no annotations provided, the description carries the behavioral disclosure burden. It does disclose UTF-8 encoding and the refusal to overwrite unless explicitly requested, which are the most important behaviors. However, it does not mention what happens on failure, whether parent directories are created, or the exact semantics of overwrite.

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 sentence with no filler. The core action is front-loaded, and the overwrite guard is stated immediately after, making the tool's key behavior easy to grasp.

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 simple three-parameter write tool, the description is minimally adequate, especially with an output schema present. However, the lack of parameter elaboration and any selection guidance leaves some burden on the agent to infer details from parameter names alone.

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?

The schema provides no parameter descriptions, so the description must compensate. It adds UTF-8 context and the overwrite refusal, but it does not explain path, content, or the overwrite flag beyond what their names already imply.

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 states a specific action and resource: 'Create a UTF-8 text file'. It also communicates the key scoping constraint around overwriting, which distinguishes it from read-only sibling tools like read_text_file, search_files, and list_directory.

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 guidance is given about when to choose this tool over siblings such as read_text_file, move_path, or delete_path. The overwrite behavior is implied, but there are no explicit alternatives, exclusions, or conditions.

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