Godot Scene Broken References

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

No annotations are provided, so the description carries full disclosure burden. It doesn't state whether this is read-only or mutation, whether it requires an open project, whether it scans the whole project or a single scene, or what the output format looks like. For a 'find/check' tool the read-only nature is implied but not confirmed.

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 a single efficient sentence with no waste. It errs toward under-specification rather than verbosity, and there is nothing redundant to trim.

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 single-parameter, no-output-schema tool with zero annotation coverage, the description must compensate heavily. It provides none of the behavioral detail (read-only vs mutation, scope, output format, error conditions). The lack of any guidance on what 'path' refers to and what results look like makes this under-specified for reliable agent use.

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 0% and the only parameter 'path' has no description or format clarifying what it should be (file path, directory, scene path in project?). The description name mentions 'scene' but it's unclear whether path points to a .tscn file, a folder, or a Godot node path string.

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 'Find broken scene resource references' uses a specific verb (find) and resource (broken scene resource references), giving a clear purpose. However, it doesn't differentiate from sibling tools like godot_scene_validate or godot_project_doctor which could plausibly also detect broken references, so sibling distinction is lacking.

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 is provided on when to use this tool vs alternatives. Siblings like godot_scene_validate, godot_project_doctor, and godot_scene_get_tree could overlap in functionality, yet no exclusions, prerequisites, or alternative references are given.

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