write_script

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

Discloses destructive nature consistent with annotations, adds details about validation refusal for uncompilable GDScript, and the exception for non-.gd files. No contradictions with 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 sentences, front-loaded with core purpose, then behavioral specifics. Every sentence adds unique value with no redundancy.

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 no output schema, the description fully explains the tool's behavior, constraints, and interactions with validation. All necessary information for correct invocation 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?

Adds meaningful context beyond the schema: explains that path must be under res://, content is self-explanatory, and validate controls whether validation is performed, with defaults and behavior per file type.

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 tool writes files under res://, distinguishes between GDScript and other text files, and specifies validation behavior. It avoids ambiguity and differentiates from sibling tools like attach_script or write_file.

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?

Provides explicit guidance on when to use: for GDScript files with validation, for other files as-is, and references build_csharp for C# compile checking. Also explains the validate parameter to force writing.

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