godot_create_script

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

The description clearly indicates a write operation and the script-file/class-extends behavior. It does not disclose what happens if `path` already exists, nor the attach-to-node side effect implied by `attach_to_node`, and the annotations provide no further safety detail beyond non-read-only status.

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?

One tight, front-loaded sentence with no filler or redundancy. It communicates target resource, action, and the key creation behavior without wasting tokens.

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?

The schema covers the parameters and an output schema appears to exist, so return-value details do not need to be restated. The remaining gap is that the tool description does not clarify the create-vs-update behavior or flag when the agent should prefer adjacent script tools, making it usable but slightly incomplete.

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?

The description adds semantic context for the `inherits` parameter via 'class extends' and for the generated script nature via 'template code'. It leaves `path`, `content`, `attach_to_node`, and `response_format` to the schema, though the nested schema descriptions are reasonably detailed once the `$ref` is expanded.

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 states a clear verb and resource: 'Create a new GDScript file'. It also distinguishes itself from sibling create/attach tools by emphasizing a script file with template code and class extends, so an agent can differentiate it from tools like `godot_create_node`, `godot_create_scene`, or `godot_attach_script`.

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 usage context is implied: use it when a new GDScript file needs to be created. However, it gives no explicit when-vs-alternatives guidance, such as when to use `godot_validate_script`, `godot_attach_script`, or `godot_get_node_script_info`, and it does not mention whether existing scripts should be updated with this tool.

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