pixel_flood_fill

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

Adds context beyond annotations: specifies connectivity rule ('exactly match seed'), return format ('JSON {canvas, seed, color}, plus rendered image on preview'), and failure format ('Error: ...'). Annotations already indicate destructive and idempotent; description complements without contradiction.

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?

Two concise sentences with a third clarifying return values; no fluff. Could use more structured formatting (e.g., bulleted return fields) but overall efficient.

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?

Missing critical detail about connectivity (4- vs 8-directional). Does not explain that the canvas file is modified (implied by destructiveHint). Return format is mentioned but key names are uncertain. For a complex operation, more precision is needed.

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 0%, meaning description does not formally describe parameters. While it implicitly references seed (x, y) and color in the main text, it omits path and preview. Schema provides parameter descriptions, but description should compensate for low coverage and does so only partially.

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?

Describes a specific verb ('flood-fill') on a specific resource ('contiguous region containing (x, y)'), explicitly distinguishing from sibling tools like pixel_replace_color or pixel_draw_pixels by naming the flood-fill algorithm and seed-based filling.

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 explicit guidance on when to use this tool vs. alternatives. The phrase 'like a paint bucket' implies a use case but does not mention other tools or provide when-not-to-use conditions.

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