Godot Scene Validate

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It doesn't state what "validate" checks for (syntax? resource paths? node hierarchy?), what happens on invalid files (error? exit code?), or whether it's a read-only operation. It could be a read operation (likely) but nothing confirms this, and there's no output schema to clarify results.

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 short sentence, which is concise. However, it is under-specification rather than efficient writing - the brevity leaves critical gaps in purpose, behavior, and usage. A single-sentence description can be high-scoring if it's dense with meaning, but "Validate a .tscn file structure" is too thin.

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 tool with no annotations, no output schema, and 0% schema description coverage, the description must compensate. It fails to explain return values, validation criteria, failure behavior, or how it differs from godot_scene_find_broken_references which sounds like a more specific validation sibling. A one-line description is inadequate for a tool operating on Godot project files.

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%, but there is only one parameter (path) whose meaning is reasonably inferable from the tool name and description. The description doesn't add any details about path format (absolute vs relative, file extension handling, project-relative paths). While the single parameter is simple, the description contributes nothing beyond what the schema shows.

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 "Validate a .tscn file structure" which uses a specific verb (Validate) and resource (.tscn file). However, it's quite terse and doesn't distinguish from sibling tools like godot_scene_find_broken_references or godot_scene_get_node, which also operate on scene files. The purpose is understandable but lacks specificity about what "validate" entails.

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 about when to use this tool versus alternatives. Given the many scene-related siblings (godot_scene_find_broken_references, godot_scene_get_node, godot_scene_list, godot_scene_get_tree), the description offers zero differentiation. There's no indication of when validation is appropriate or what problems it detects versus the broken-references checker.

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