Create stipple point cloud

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a mutation tool but not destructive. The description adds useful behavioral context: it outputs a Render TOP through a Geometry COMP in points render mode. No contradictions with annotations.

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, well-structured paragraph. It front-loads the core purpose, lists modes, and mentions siblings. Every sentence adds value, 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?

With 11 parameters, 100% schema coverage, and no output schema, the description covers the overall output (Render TOP through Geometry COMP) and explains visual modes. It provides enough context for an AI agent to understand the tool's behavior and output, but could optionally include a note about the return value or pipeline steps.

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%, meaning all 11 parameters have descriptions. The description provides overall conceptual context but does not add significant detail beyond what the schema already provides. A baseline of 3 is appropriate.

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 starts by clearly stating the tool's purpose: 'Density-weighted particle scatter rendered as discrete points — a stippled/halftone-engraving point cloud'. It explicitly distinguishes from three sibling tools: create_pop_geometry, create_dither, create_halftone, making it easy to select the correct tool.

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 explains when to use this tool (for stippled/halftone point clouds) and lists three visual modes. It directly contrasts with siblings: create_pop_geometry for procedural SOP geo, and the rasterized create_dither/create_halftone for TOP-space operations. This provides clear guidance on alternatives.

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