game_set_particles

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only implies mutation through 'Configure'. It does not state whether existing settings are overwritten, whether processMaterial is merged or replaced, what happens on an invalid nodePath, or whether changes apply immediately.

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 non-redundant sentence that front-loads the core message. It is appropriately brief, though the brevity is achieved mainly by omitting detail rather than by distilling richer content.

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?

For a tool with 9 parameters, a nested processMaterial object, no annotations, and no output schema, one generic sentence is insufficient. Crucial context — prerequisites, effect semantics, and error behavior — is missing, though the schema's 100% parameter coverage softens the gap.

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 100%, so all 9 parameters are already documented with concise descriptions in the schema. The tool description adds no parameter-level context, so the 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?

The description states a specific verb ('Configure') and resource ('GPUParticles2D/3D node properties'), going beyond the tool name to specify the node family. It stops short of a 5 because it offers no differentiation from generic setters like game_set_property, which could also target particle nodes.

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, no prerequisites (e.g., the target node must already exist in the scene), and no exclusions or alternatives. With overlapping siblings like game_set_property and game_spawn_node, an agent must guess when this tool is the right choice.

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