paste_grid

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

No annotations are provided, so the description carries full burden. It explains the character encoding and behavior of '.' as transparent, but does not explicitly state that the operation is destructive (overwrites pixels) or mention other behavioral traits like boundary handling.

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, both concise and front-loaded with essential information. It packs the entire character mapping and usage intent into a single sentence, with no redundant 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?

Given the complexity (10 parameters, 4 required) and lack of output schema or annotations, the description covers the core functionality well. It explains the input format and key parameters, though it doesn't describe return values or error handling, which is acceptable for a write tool.

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%, so baseline is 3. The description adds significant value by explaining the grid text format (character mapping to palette indices) and the meaning of '.' and other characters, which goes beyond the schema's description of 'Rows of palette-index characters'.

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 'Bulk-write a region from grid text', specifying the verb (write), resource (region), and format (grid text with character mapping). It distinguishes from sibling tools like paste_stamp which likely paste image data.

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 says 'The workhorse for blocking in shapes', implying it is the primary tool for that task and suggesting when to use it. However, it does not explicitly state when not to use it or provide alternatives, but the sibling list offers other drawing tools.

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