inject_script_autoload

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

No annotations, so the description carries the burden. It usefully discloses that the tool mutates project.godot and requires a pre-existing script, but it says nothing about failure behavior, whether a backup is made, load-order placement, or what happens when the singleton name collides beyond what replaceExisting in the schema implies.

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, the action and the file it touches are front-loaded, and the constraint follows. No filler.

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?

For a mutation tool with no annotations and no output schema, the description covers the target file, the required input shape, and the key precondition. Missing only edge-case behavior (duplicate names, load order, rollback), which is a modest gap.

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 100%, so the baseline is 3. The description reinforces the res:// and existence constraints on scriptPath, but adds no semantics beyond the schema for projectPath, singletonName, or replaceExisting.

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?

Specific verb (add) plus resource (GDScript as a Godot global Autoload singleton) and the mechanism (editing project.godot). This clearly separates it from siblings like create_gdscript or generate_tscn_scene.

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?

States prerequisites explicitly: the script must already exist and must use a res:// path. It does not name an alternative tool or say when not to use it, which keeps it short of a 5.

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