validate_scene

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 only says 'Validates .tscn' without detailing what validation checks (syntax, resources, references), what the tool returns (success/failure, error messages), or any side effects. This is insufficient for an agent to understand the tool's behavior beyond the bare action.

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 extremely concise (four words), which is efficient, but it is under-specified to the point of lacking essential details. While it is front-loaded with the verb and resource, the brevity does not serve the agent's needs; it is more under-specification than appropriate conciseness.

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 one parameter, no output schema, and no annotations, the description is expected to provide a complete picture of the tool's purpose, parameters, and behavior. It fails to do so—it gives no information about expected inputs, validation outcomes, or how to interpret results, making it inadequate for reliable invocation.

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 input schema has zero description coverage, and the description does not mention the scene_path parameter at all. The agent must guess that scene_path refers to the file path of the .tscn file, but no additional meaning or format guidance is provided, leaving the parameter semantics completely undisclosed.

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 a clear verb ('validates') and a specific resource ('.tscn'), which identifies it as a validation operation for Godot scene files. This distinguishes it from sibling tools like validate_script (script validation) and run_scene (execution), though it doesn't explicitly mention those alternatives.

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 validate_scene versus alternatives like validate_script or inspect_scene_tree. The description does not explain the context for validation, such as pre-export checks or debugging, leaving the agent to infer usage from the tool name alone.

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