stamp_pattern

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

With no annotations, the description carries full burden. It reveals compositing options (opacity, blend_mode), gap spacing, and that the region defaults to the whole canvas. However, it does not disclose side effects (e.g., permanent modification), undo behavior, or performance considerations. It is partially transparent but missing key behavioral traits.

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 relatively concise, starting with a clear purpose sentence followed by a parameter list. It uses minimal prose and front-loads the key action. It could be more structured but is not overly verbose.

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 tool with 12 parameters, no output schema, and no annotations, the description is insufficiently complete. It misses required parameters (filename) and provides no information about return values or side effects. The parameter list is partial, reducing completeness.

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 description adds meaning for some parameters (e.g., 'Image/sprite to tile', 'Gap between tiles') but omits required parameters like 'filename' and does not mention 'frame' or 'layer'. Given 12 parameters and 0% schema description coverage, the description should cover all parameters but fails to do so completely.

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 'Tile an image/sprite across a region to fill it with a repeating pattern.' This is a specific verb+resource combination and distinguishes it from siblings like stamp_file (single placement) or draw_image_base64 (single image).

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 on when to use this tool versus alternatives (e.g., stamp_file, draw_rectangle). There is no mention of prerequisites or typical use cases, leaving the agent to infer context from the description alone.

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