script_create

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

No annotations are provided, so the description must disclose behavioral traits. It lacks critical details: whether the tool creates a file on disk or returns text, what side effects occur, and what permissions are needed. The description is vague about the output's nature.

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 sentence with no wasted words. However, it could be more structured (e.g., bullet points for parameters) to enhance readability. Still, it is appropriately concise for a simple tool.

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 tool has 5 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the return value, error behavior, or how parameters affect the template. The description leaves many questions unanswered.

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 0% parameter description coverage, and the description only vaguely references the parameters ('extends, class_name, lifecycle functions, and signals') without explaining each parameter's role. For example, includeReady, includeProcess, and includePhysicsProcess are not explained beyond the generic term 'lifecycle functions'.

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 clearly states the tool generates a GDScript file template for a node type, listing specific elements like extends, class_name, lifecycle functions, and signals. This is a specific verb-resource combination that distinguishes it from sibling tools like script_info or gd_lsp_*.

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 implies usage when creating a new script template, but it does not provide guidance on when to use this tool versus alternatives (e.g., when to use script_list or script_info instead). No mention of prerequisites or constraints.

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