scripts

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

The description adds behavioral details beyond annotations, such as 'replace entire file' for write and 'link to scene node' for attach. Annotations already indicate destructiveHint true, but the description provides specific mutation 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?

The description uses bullet points to organize actions and parameters, making it scannable. It is relatively concise, though the list could be more compact. Every sentence adds value.

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?

Given the 100% schema coverage and rich action descriptions, the tool is mostly complete. However, it lacks explicit return value descriptions (no output schema) and error handling notes, which would enhance completeness.

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 description enhances schema by listing required vs optional parameters per action and providing a usage example for script_path. Schema coverage is 100%, so baseline is 3, but the added action-specific parameter grouping justifies a 4.

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 uses 'GDScript file CRUD' and lists each action (create, read, write, attach, list, delete) with specific verb+resource pairs. It clearly distinguishes each action, covering all operations for GDScript files, making purpose highly clear.

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?

The description lists required and optional parameters for each action, guiding the agent on which parameters to provide. However, it does not explicitly state when to use this tool versus sibling tools, though sibling names are distinct enough to infer usage context.

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