blender_geonode_scatter_instances

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

With no annotations provided, the description must carry the burden of behavioral disclosure. It says it builds a complete Geometry Nodes setup, but does not state whether it creates a modifier, overwrites existing node trees, makes instances live, or what side effects occur in the scene.

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?

Two efficient sentences with the core promise front-loaded in 'One-call scatter.' The feature list is compact, relevant, and contains no wasted words.

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 description is thin for a 9-parameter mutating tool with no annotations and no output schema. It omits important context: whether target and instance objects must already exist, what the function returns, whether a modifier is added to the target, and whether existing Geometry Nodes setups are overwritten.

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 the schema already documents all 9 parameters. The description's feature list ('density, Poisson-disk spacing, random scale range...') mirrors the schema descriptions and adds no new semantic detail beyond the baseline.

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 uses a specific verb ('build'), names the resource ('complete Geometry Nodes setup'), and states the operation ('distributes instances ... across surface of another'). It clearly describes what the tool accomplishes, though it doesn't explicitly distinguish itself from sibling tools like blender_scatter_on_surface.

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 explicit guidance is given about when to use this tool versus sibling alternatives such as blender_scatter_on_surface or the lower-level geonode tools. 'One-call scatter' implies a high-level use case, but there are no stated prerequisites, exclusions, or alternative routing.

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