godot_configure_particles

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

The description provides zero behavioral disclosure beyond the annotations. With all hints false (not readOnly, not destructive, not idempotent), the description should clarify side effects such as node creation, file saving, or mutation semantics, but it makes no mention of these.

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 single sentence is concise but severely under-specified for a tool with many parameters. It lacks any structure, front-loading of critical constraints, or organization that would help an agent quickly grasp its scope.

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?

Despite a rich schema and output schema, the description fails to explain return values, whether the tool creates or modifies nodes, or how to choose between node_name and node_path. It is incomplete for such a multifaceted tool.

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 information about the 18+ parameters. The schema has descriptions, but the context reports 0% schema description coverage, so the description must compensate. It does not, leaving agents without guidance on parameter usage.

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 the verb 'Configure' and the resource 'GPUParticles2D/3D or CPUParticles2D/3D node emission', clearly distinguishing it from general node manipulation tools. It is specific and not a tautology, though it doesn't enumerate the exact emission attributes that can be adjusted.

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 versus alternatives such as godot_create_node or godot_modify_node. It doesn't explain whether it creates new nodes, modifies existing ones, or both, leaving the agent to infer usage from the schema.

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