write

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 clearly discloses the destructive overwrite behavior and the side effect of creating parent directories. It also adds a caution about data loss, which is valuable transparency beyond the schema.

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 extremely tight: the first sentence states the core action, the second clarifies overwrite behavior, and the final paragraph adds an important warning and sibling alternative. No word is wasted, and the key facts are front-loaded.

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 two-parameter write tool with no output schema or annotations, the description covers the essential context: purpose, overwrite/destructive behavior, parent directory creation, and guidance for using the alternative `edit` tool. It doesn't detail error cases, but the information needed to invoke it correctly is present.

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 meaning by stating that missing parent directories are automatically created (path behavior) and that content is the complete replacement, reinforcing that partial changes should go to `edit`. This goes beyond the schema's simple descriptions.

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: it writes a file, automatically creates missing parent directories, and overwrites existing files. It explicitly distinguishes itself from the `edit` tool by directing partial changes elsewhere, so an agent can tell them apart immediately.

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 provides explicit when-not guidance: for partial changes to existing files, prefer the `edit` tool. It also warns to ensure complete file context before modifying existing files, which is a clear usage prerequisite.

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