canvas_batch

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

With no annotations provided, the description carries full burden. It discloses that all instructions are executed and the canvas is auto-exported, returning the final ASCII result. However, it does not mention whether a canvas_new instruction is required first, error handling, or state reset behaviors.

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 two sentences, front-loaded with the core purpose, and explains the ops parameter efficiently without redundant details.

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?

For a batch tool with nested schema and no output schema, the description provides a clear overview of input structure and output (final ASCII). It could benefit from noting the necessity of canvas_new or error behavior, but overall it is sufficiently complete for an agent to understand the tool's role.

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 parameter details (ops array with specific op types and required fields), so the description's high-level explanation of 'ops is an instruction array...' adds minimal value beyond the schema. The 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 clearly states 'batch execute drawing instructions and return final ASCII result', identifying the tool as a batch operation for drawing. This distinguishes it from sibling tools that handle individual drawing operations like draw_box, draw_line, etc.

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 tool's name and description imply it is for executing multiple drawing instructions in sequence. Sibling tools (draw_box, draw_line, etc.) serve as single-operation alternatives, but the description does not explicitly state when to choose one over the other, only indicating batch execution.

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