game_csg

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

With no annotations, the description must fully disclose behavior. It only states 'create/configure CSG nodes with boolean operations' but omits critical details: whether operations are destructive, what happens to existing nodes, error handling, or dependency on scene structure. This is insufficient for a tool that modifies scene geometry.

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 sentence, very concise and front-loaded with the core purpose. However, given the tool's complexity (10 parameters, boolean operations), it could benefit from a brief expansion to cover key usage scenarios.

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 is complex with 10 parameters, nested objects, and no output schema. The description fails to explain how boolean operations work with different CSG types, prerequisites (e.g., parent node must exist), or return value (success indication, new node path). Incomplete for an AI agent to use correctly.

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% with parameter descriptions, so baseline is 3. The tool description adds no extra meaning beyond the schema. Parameters like 'action', 'csgType', and 'operation' are briefly described in schema but the description doesn't clarify their interplay (e.g., which types support which operations).

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 explicitly states the tool creates/configure CSG nodes with boolean operations, clearly identifying the verb (create/configure) and resource (CSG nodes) and the key feature (boolean operations). This distinguishes it from sibling tools, none of which mention CSG.

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 provides no guidance on when to use this tool versus alternatives, such as other node creation tools (e.g., game_spawn_node, game_mesh_instance). It lacks context for when to create vs configure, or boolean operations vs other geometry manipulation.

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