validate_script

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 .gd' – no mention of whether it is read-only, returns a result, throws errors, or has side effects. An agent has no idea what happens when called or what a successful/failed validation looks like.

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 short (two words), which some might call concise, but it is under-specified rather than appropriately sized. It lacks any structure or front-loaded critical information. Every word must work hard, and here they do not – they only restate the tool's name.

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 validation tool with one parameter, no output schema, and no annotations, the description is far from complete. It does not explain what validation checks, what the return value is, whether it modifies anything, or how errors are reported. An agent given only this description would be guessing at nearly every aspect of 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 schema has one parameter script_path with no description (schema coverage 0%). The description adds zero meaning about what script_path should contain (e.g., a file system path, relative path, content string). The name suggests 'path' but no detail is given to help an agent construct a correct invocation.

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 verb ('Validates') and a resource ('.gd' files), which gives a basic sense of purpose. However, it is vague about what validation entails (syntax? semantics? linting?) and could be confused with validate_scene, which also validates something. It barely exceeds a tautology because 'validate_script' already implies validating a script.

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 guidance on when to use this tool vs. alternatives like validate_scene, format_gdscript, or run_tests. No mention of prerequisites, typical use cases, or conditions that would lead an agent to choose this over siblings. The description provides zero routing information.

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