godot_configure_gltf_import

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

The description only says 'configure', which is at least consistent with annotations (readOnlyHint=false). However, it does not disclose the main behavioral side effect that the schema hints at: the reimport option can immediately trigger a reimport via EditorFileSystem, or that import settings are persisted. With minimal annotation detail, this leaves the side-effect profile under-specified.

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?

One terse sentence with no filler, front-loaded with the verb and the exact asset type. It is appropriately sized for a tool whose parameter detail lives in the schema.

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 definition is minimally viable for selecting the tool, and the schema fills in parameters and likely output. It remains incomplete as a standalone description because it omits the reimport side-effect and does not distinguish this from asset reimport/instantiation flows.

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 description adds no parameter-level meaning, but the input schema already documents all parameters in detail (model_path example, reimport trigger, LOD options, material extraction, shadow mesh, skeleton bones). Baseline 3 applies because the schema carries the parameter semantics.

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?

States a specific action ('configure') and a clearly scoped resource ('GLTF/GLB 3D model import presets'), which distinguishes it from sibling configure tools that target particles, rendering, environment, etc. The resource is independent enough that no schema inspection is needed to tell them apart.

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 the use case: adjusting import presets for GLTF/GLB model assets. It does not state when to prefer this tool over related alternatives such as godot_reimport_asset or godot_configure_lod_manager, nor does it give exclusions.

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