script_create

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

With no annotations, the description carries full burden. It discloses key behaviors: writes to disk, overwrites existing files, triggers a filesystem scan, and details sidecar file handling (cleanup.rm listing for new files, omission for overwrites). It does not cover permission requirements or error impacts, but provides solid transparency.

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 three sentences, each serving a distinct purpose: stating core action, specifying write behavior, and detailing sidecar nuances. It is front-loaded with the primary goal and efficient, with no extraneous 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?

Given 3 parameters and an output schema, the description covers creation, overwriting, filesystem scan, and sidecar behavior comprehensively. It omits error handling or return value details, but the output schema likely handles those. Overall adequate for a write tool with moderate complexity.

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. The description adds minor value: clarifies path format ('res://'), explains that empty content creates a blank file, and notes session_id targets a Godot session. This matches or slightly extends schema descriptions but does not significantly compensate beyond baseline.

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 creates a new GDScript source file (.gd) on disk, with a specific verb ('Create') and resource. It includes details about writing content, overwriting, and triggering a filesystem scan, distinguishing it from sibling tools like script_patch or script_manage.

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 creating .gd files and mentions overwriting behavior, but it lacks explicit guidance on when not to use this tool or alternatives (e.g., script_patch for modifications). No exclusions or context for choosing between siblings.

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