game_gi

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

No annotations provide destructive or read-only hints. The description implies mutability but does not disclose side effects (e.g., whether it overwrites existing nodes), required permissions, or what 'configure' entails beyond creation.

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?

Single sentence, no wasted words. While it could include more context, it is appropriately concise for a tool that is one of many.

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?

No output schema, and description lacks detail on return values or behavioral expectations. GI is a complex concept; minimal description does not sufficiently guide an AI agent on usage and outcomes.

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%, so the schema already describes parameters. The description adds no extra meaning beyond mapping 'voxel_gi'/'lightmap_gi' to giType. Baseline 3 applies.

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?

Description clearly states the tool creates/configures two specific GI types (VoxelGI or LightmapGI), using a specific verb and resource. It distinguishes from sibling tools like game_light_3d or game_environment.

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 on when to use this tool vs alternatives such as game_environment or game_light_3d. Does not mention prerequisites or typical scenarios.

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