art.canvas.draw_dither

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

There are no annotations to carry the behavioral burden, and the description gives no detail about side effects, whether the operation is destructive, coordinate constraints, or expected results. The verb 'apply' implies mutation but nothing else is disclosed.

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, focused sentence communicates the core operation without filler or redundancy. It is well-structured and immediately understandable.

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 minimally viable for invoking the tool because the schema documents all parameters. However, without annotations or extra behavior details, an agent lacks contextual information about session requirements, visual outcomes, or distinctions from neighboring canvas tools.

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 parameters already carry individual descriptions. The tool description adds no parameter-level context, but no additional meaning is strictly needed given the schema's completeness.

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 clearly states a specific action ('apply a dither pattern') on a specific resource ('rectangular region'), which conveys the primary purpose. It does not explicitly differentiate among sibling canvas tools, but the dither-pattern concept provides enough distinction in most cases.

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 usage context or alternative routing is provided. The description does not explain when an agent should choose draw_dither over related tools like draw_noise, fill, or draw_rect.

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