Create resource

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

The description mentions it fails if target exists unless overwrite=true, which is useful. However, it does not disclose success behavior, side effects, or prerequisites like project root and permissions. With no annotations providing safety hints, more detail would be beneficial.

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 with two sentences. The first sentence clearly states purpose, and the second adds a critical failure condition. Every sentence serves a purpose with no wasted words.

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 8 parameters, 2 required parameters, and a dense sibling list with overlapping tools, the description is incomplete. It does not explain the relationship to sibling tools, what happens on success, or the meaning of 'template'. The lack of output schema makes this gap more significant.

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 coverage is 100%, so the base score is 3. The description adds minimal extra meaning beyond schema, such as reiterating kind values and overwrite behavior, but does not explain complex parameters like base or root_type beyond what is in the schema.

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 creates a new resource from a template with specific supported kinds (gdscript, csharp, scene, resource). However, it does not distinguish itself from sibling tools like create_scene, create_script, or create_resource, which exist separately and could cause confusion.

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 this tool versus the separate create_scene, create_script, or create_resource tools. The description lacks explicit context for when this combined approach is preferable.

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