art.canvas.draw_noise

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

No annotations are provided, so the description must bear the full behavioral burden. It does not disclose whether existing pixels get overwritten, how hidden randomness is handled, whether density affects the probability of each pixel, or what side effects may occur. Since this is a mutating canvas operation, the lack of any destructive-impact context becomes significant.

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 one single purpose-driven sentence with no filler or redundant information. The verb and core concept come first, and the object and how it is created follow immediately; every word earned its place.

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?

Given 7 parameters, no annotations, no output schema, and a large sibling set of drawing tools, the description is incomplete on its own. An agent lacks information about when to use noise versus dither or fill, what happens to existing content, and what the semantic role of density is beyond the schema default. The schema covers parameters, but the contextual essence and side-effect clarity are missing.

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 schema covers all parameters in 100% of cases, so the baseline is already 3. The description adds the relation that 'specified colors' means the random pick palette and 'region' maps to x, y, width, and height. It does not need to explain density because the input schema already has a clear description for it.

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 names a specific verb ('Fill') and resource ('a region') plus the defining behavior ('with random noise using specified colors'). This distinguishes it from solid fills, lines, and dithering operations without naming alternatives. It is not a 5 because it does not explicitly contrast with similar canvas tools.

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 is given for when to use this tool versus art.canvas.fill, art.canvas.draw_dither, or art.canvas.batch_draw. The description only explains the mechanism, leaving an agent to infer selection from the word 'noise' alone.

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