write_file

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

No annotations are present, so the description carries the full burden. It mentions UTF-8 encoding, which is a useful detail, but it does not disclose whether existing files are overwritten, if directories are auto-created, or any error behavior. This is a significant gap for a write operation.

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 concise sentence with no extraneous words. It is front-loaded and easy to parse, but it could beneficially include more behavioral details without becoming verbose.

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 there is no output schema and no annotations, the description alone must provide a complete picture. It only states the primary action, omitting side effects, return values, path validation, and interactions with project structure. This is inadequate for a tool with four parameters and potential destructive behavior.

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 description coverage is only 25% (only 'projectPath' has a description). The description does not compensate by explaining 'path' or 'content'. While 'path' and 'content' are self-explanatory, the absence of any parameter context means the agent must infer semantics, and the default behavior of 'createDirectories' is only in the schema.

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 action ('Write') and the resource ('a UTF-8 text file') with a specific location ('inside a Godot project'). It distinguishes from 'read_file' but does not explicitly differentiate from 'create_script' or other write-related tools.

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?

No guidance is provided about when to use this tool versus alternatives. There is no mention of overwriting files, creating scripts via 'create_script', or any prerequisites like an open project.

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