godot_script

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

With no annotations, the description must disclose behavioral traits. It lists actions but does not explain what each does (e.g., 'attach, detach' are unclear), side effects, permissions, or limitations. The path constraint is mentioned but not elaborated.

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 concise with one sentence and a list. It front-loads the key action list. However, it could be more structured by grouping similar actions or providing brief explanations.

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 the tool's complexity (multiple actions, no output schema, no annotations), the description is far too minimal. It lacks details on each action's behavior, required parameters, return values, and error conditions. An agent cannot reliably use this tool without additional information.

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 0%, so the description must add meaning. It lists possible actions (read, create, edit, etc.) but does not describe the 'params' parameter at all. The action values are not formally defined, and no format or constraints are provided.

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 'GDScript file ops' and lists specific actions, clearly indicating the tool is for GDScript file operations. It distinguishes from sibling tools like godot_scene or godot_node_read by focusing on script files. However, it doesn't explicitly state the tool operates on files under the res:// path, which is only mentioned in passing.

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 on when to use this tool versus alternatives. The description does not mention when not to use it or suggest sibling tools for different tasks. Usage is implied but not explicitly stated.

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