godot_instantiate_model

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

The description mentions 'active scene' as a context but does not disclose side effects beyond the implied mutation (creating an instance). It does not note whether the operation is destructive, requires saving, or what happens if the source_path is invalid or the scene is unsaved. Annotations are minimal (destructiveHint: false, but no explanation given), so the description carries the burden and under-delivers.

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, clear, front-loaded sentence with no redundancy. It loses one point for omitting any usage or behavioral detail that would help an agent, but it is efficient and scannable.

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 schema is rich and covers parameters in detail, but the description lacks contextual guidance about the tool's side effects (modifying the active scene) or when a user might want to use save_as_scene_path. For a moderately complex tool, the description is a minimal but acceptable overview.

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 input schema is rich and covers all parameter meanings (types, defaults, descriptions) with 100% coverage. The description itself adds nothing beyond the tool's general purpose, which is acceptable given the schema's completeness—baseline 3.

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 states a specific action ('Instantiate') with a clear object ('3D model asset') and destination ('into the active scene'). It distinguishes this as a creation tool, though it doesn't explicitly differentiate from sibling tools that also operate on the scene tree (e.g., godot_create_node or godot_add_child).

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 given about when to use this tool versus alternatives, prerequisites (e.g., an active scene must be open), or situations where it is not appropriate. The description is purely descriptive with no routing hints.

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