save_text_file

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

Discloses key behaviors: default refusal to overwrite with error, overwrite=true to replace, parent directory creation, and return format. Lacks details on encoding or permissions, but sufficient for a simple file write.

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?

Four efficiently written sentences. First sentence states purpose, followed by key behaviors. No redundant or missing 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 purpose, default behavior, overwrite option, directory creation, and return value. Missing error cases beyond overwrite refusal, but acceptable for a simple tool with no annotations or output schema.

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 baseline is 3. Description adds context like 'returns 409 error' and 'creates parent directories', but mostly parallels schema 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?

Clearly states 'Write text content to a file at a given path', specifying the verb (write) and resource (text content to file). No sibling tool performs the exact same function, so it stands out.

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?

Implicitly describes when to use (to write text files) and explains overwrite behavior, but does not explicitly state when not to use or compare with alternatives like export_soul_file_to_path.

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