godot_validate_scene

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

With no annotations, the description carries the full behavioral burden and delivers almost nothing: it does not say whether validation is read-only, what kinds of problems it detects (syntax, missing dependencies, broken references), or what happens on invalid input. Only the word 'validate' implies non-mutating behavior.

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 short sentence with no filler, which is appropriately terse. However, the brevity reflects under-specification rather than disciplined editing, so it earns only a middling score.

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?

There is no output schema and no annotations, so the description should explain what a validation result contains (errors, warnings, success indicator). Combined with the undocumented path parameter, an agent cannot confidently predict the call's behavior or response.

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 single required parameter 'path' has 0% schema description coverage, so the description must explain it but does not. It never clarifies whether the path is a filesystem path or a res:// project path, or whether directories are accepted.

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?

"Validate a project scene" gives a specific verb and resource, so the general intent is clear. But it never distinguishes itself from siblings like godot_scene_inspect or godot_run_check, leaving the agent unsure what 'validate' covers versus inspecting or running a check.

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?

There is no statement of when to call this versus godot_scene_inspect, godot_run_check, or godot_script_diagnostics, and no prerequisites or failure conditions are mentioned. The agent must infer usage purely from the name.

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