create_script

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

Annotations provide only a title, no readOnlyHint or destructiveHint. The description states 'Create' implying mutation, but does not disclose side effects, prerequisites, or error conditions. The minimalist description fails to compensate for missing annotation details.

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?

A single concise sentence conveys the core purpose with no wasted words. Though brief, it is front-loaded and efficient. Minor improvement could add structured detail without losing brevity.

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?

The tool has 6 parameters, 2 required, no output schema, and many siblings. The description lacks details on return values, error handling, template behavior, and proper usage. Inadequate for a tool with moderate complexity.

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 100% (all 6 parameters have descriptions). The description adds no extra meaning beyond the schema. Baseline score of 3 applies as the schema already documents parameters.

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 a specific verb ('Create'), a clear resource ('GDScript file'), and a method ('from a template'). It distinguishes from siblings like attach_script (attaches existing script) and create_resource (generic resource).

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 on when to use this tool vs alternatives (e.g., attach_script, create_scene). The phrase 'from a template' hints at a specific use but lacks explicit context or exclusions.

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