Write File

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds value by explicitly stating 'OVERWRITING ALL existing content' and that it creates parent directories. This provides behavioral clarity beyond annotations, though idempotency is not mentioned (but annotation says false).

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 sentences, front-loaded with purpose and key warning about overwriting. No redundant or vague phrasing. Every sentence adds essential information.

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 purpose, overwrite behavior, and directory creation. With an output schema present (though not detailed here), nothing critical is missing. Could mention that content will be written as-is (string), but schema already specifies type. Overall sufficient for a write 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 100%, so baseline is 3. The description does not add new parameter-level details beyond what the schema provides ('path' with description 'Absolute path to file or directory', 'content' as 'Content to write'). No additional semantic value is added.

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 'Write content to a file, OVERWRITING ALL existing content.' It specifies the verb (write), resource (file), and key behaviors (overwrite, create parents). This distinguishes it from siblings like 'edit' or 'apply_patch' which modify partially.

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 implies it can be used for creating new files (since it creates parent directories) and overwriting existing ones. However, it does not explicitly state when to use this over siblings like 'edit' (for partial changes) or 'search_and_replace' (for targeted modifications). Usage context is clear but lacks explicit alternatives.

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