write_file

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

Discloses key behaviors: UTF-8 encoding, sandbox directory, parent directory creation, and size limit refusal. Lacks details on overwrite=false behavior and encoding error handling, but good given no annotations.

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 concise sentences, front-loaded with main action, no redundant 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?

Covers sandbox, encoding, directory creation, size limit, but lacks error handling details and default overwrite behavior. Output schema exists but not referenced.

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?

Describes path as relative and content as UTF-8 text, but does not mention the overwrite parameter. With 0% schema coverage, partially compensates.

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?

Clearly states it writes UTF-8 text to a file within a sandboxed directory, distinguishing from sibling tools like read_file 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?

Implies usage via sandbox context but does not explicitly state when not to use or provide alternatives beyond the sandbox restriction.

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