fill_checkerboard

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

Annotations declare readOnlyHint=false and openWorldHint=false, so the agent knows this mutates a closed-world resource. The description adds no further behavioral context: it does not say whether existing pixels are overwritten, how the region is bounded, whether a selection or layer is required, or what side effects occur.

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 a single front-loaded sentence with no filler. It is efficient, though notably sparse for a 10-parameter tool.

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?

With 10 parameters, no output schema, and only minimal annotations, the description is too thin. It omits how the region is defined, which parameters are required, what layer or file is affected, and what happens to existing content.

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 40%, with only default-value notes for x, y, size, and frame. The description only clarifies that `size` is in pixels; it does not explain the coordinate/region parameters, width, height, layer, filename, or color1/color2, so it does not compensate for the low coverage.

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?

States a specific verb ('Fill') and resource ('region') plus the distinguishing checkerboard pattern and square size. It does not explicitly differentiate itself from siblings like fill_area, fill_layer, or stamp_pattern, so it falls short of a 5.

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?

Provides no guidance about when to use this tool instead of related fill or pattern tools such as fill_area, fill_layer, or stamp_pattern. It only describes the operation, leaving the agent to infer usage context.

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