docker_write_file

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

With no annotations, the description carries responsibility for behavioral disclosure. It reveals create/overwrite and append behavior, plus the 'directly' aspect, but omits prerequisites like a running container, permissions, or return values. This is adequate but not thorough.

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, front-loaded sentence with no filler. Every clause adds useful information: what it writes, where, and the append alternative.

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 mutation tool with no annotations and no output schema, the description is minimally complete. It states the core behavior and the schema covers all parameters, but it lacks information about prerequisites, side effects, and return values. Given the tool's simplicity, this is acceptable though not comprehensive.

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 a little extra meaning by specifying 'UTF-8 text content' and the append behavior, but it mostly echoes the schema's parameter descriptions without adding significant new semantics.

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 uses a specific verb ('Write') and resource ('a file inside a Docker container'), clearly distinguishing it from siblings like docker_read_file or docker_mkdir. It also notes create/overwrite behavior, reinforcing the tool's unique purpose.

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 usage for writing text content directly, as opposed to copying files (docker_cp_to), but does not explicitly name alternatives or state when not to use it. The append hint gives some usage context, but no clear exclusions.

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