write_text_file

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

Annotations already mark the tool as destructive and not read-only. The description adds beyond-annotation behavior: parent folders are auto-created and encoding can be set. It does not explicitly spell out overwrite semantics, but the append parameter and destructive hint cover the key risk.

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?

Two short bilingual sentences front-load the main behavior and immediately follow with concrete use cases. Every clause earns its place, with no placeholder or tautological wording.

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 file-writing tool with fully documented parameters, destructive annotations, and no output schema, the description covers purpose, effects, and use cases sufficiently. It could be more explicit about overwrite-by-default behavior, but the append parameter and destructive hint make this recoverable.

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 100%, so the baseline is 3. The description adds meaningful path semantics by telling the agent that missing parent directories will be created automatically, and it points to the encoding option. The phrase 'optional UTF-8' is slightly imprecise because utf-8 is the default and ansi is the alternative, but the schema resolves this.

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 verb and resource ('Write a text file') and adds scope: it automatically creates parent folders and supports encoding. This makes the tool's purpose unambiguous and distinguishes it from siblings like read_text_file or delete_file.

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?

It explicitly gives use cases ('emit batch scripts, export manifests or custom configs'), which is clear context for when to invoke it. It does not name alternatives or exclusions, so it stops short of full when-to-use versus when-not-to-use guidance.

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