write_file

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that the tool will overwrite an existing file, which is a critical destructive behavior. However, it does not disclose other potentially relevant details such as whether parent directories are created or what happens on invalid paths.

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 a single sentence, frontloaded with the core action. It includes the important overwrite caveat without unnecessary eloquence, earning its place.

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?

Given the tool's simplicity (two string parameters) and the presence of an output schema, the description is sufficiently complete for an agent to use it correctly. It explains the primary action and the destructive edge case without needing excessive detail.

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 has zero description coverage for its two parameters (path, content), so the description must compensate. It adds meaning by specifying 'text content,' which clarifies the content parameter, and the phrase 'Create a file' implies the path parameter is the target file location. However, it does not provide details on expected path formats or content encoding.

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's function: 'Create a file (or overwrite it if it exists) with the given text content.' This uses the specific verb 'Create' and resource 'file,' and explicitly differentiates from sibling tools like delete_file, read_file, and update_file by noting the overwrite behavior.

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 the tool should be used to create or overwrite files with text content, but it does not explicitly provide guidance on when to use write_file versus sibling tools like update_file. No alternatives are mentioned, so the usage context is only implicit.

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