apply_template

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

Describes core behavior: copying files, setting/opening main_scene, and the force parameter for overwrites. The annotations (destructiveHint: false) are mildly contradicted by the ability to overwrite files, but the description clarifies that overwriting requires explicit force. Missing details on error handling or return values.

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 relatively concise (two main sentences) and front-loads the primary action. The extra sentence about generic templates is somewhat redundant but not overly verbose. Could be slightly tighter.

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's moderate complexity (file copying, main_scene handling, overriding), the description covers the essential aspects but omits details like return values, error scenarios, or what happens if the template lacks files. No output schema further increases the need for clarity.

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%, and the description adds context: for 'template' it gives an example ('platformer-2d') and explains that calling without it lists available templates. For 'force', it describes the default behavior. This adds meaning beyond 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 action: instantiate a bundled or project template into res://, copying files and optionally setting/opening a main_scene. It distinguishes this tool from siblings by its unique purpose of template instantiation; no other sibling tool serves this function.

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?

Provides explicit guidance: 'Call with no template to list what's available.' Also explains that project templates override bundled ones. However, it does not specify when not to use this tool or compare it directly to alternatives, though the context makes it clear this is the only template-related tool.

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