create_vehicle_body

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 only states that the tool creates a VehicleBody3D with wheels, but does not mention side effects (e.g., whether existing nodes are overwritten), requirements (e.g., valid scene_path), or default wheel behavior. This is a significant gap for a mutation tool.

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 clear sentence with no fluff, but it is under-specified. It front-loads the purpose but lacks any additional context, making it more incomplete than concise.

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 tool has four parameters (one required) and no output schema, yet the description explains none of the parameter semantics or expected behavior. There is no mention of how wheels are configured, what scene_path must point to, or what the tool returns. The description is inadequate for an agent to use the tool effectively.

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 description coverage is 0%, so the description must compensate. It mentions 'VehicleWheel nodes' but does not explain the four parameters (name, parent, wheels, scene_path) or their meanings. An agent cannot infer that 'wheels' expects an array of objects with name/position/suspension fields, nor what 'parent' or 'scene_path' signify.

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 (Create) and resource (VehicleBody3D) with the additional detail 'with VehicleWheel nodes for car physics,' which distinguishes it from other create_* tools. It clearly conveys what the tool does without ambiguity.

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?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites, when not to use, or reference to related tools such as read_vehicle_body or create_scene. The description only states the action, leaving context entirely absent.

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