draw_symmetric_pixels

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

No annotations are provided, so the description carries the burden. It explains modes and axis defaults, but does not disclose whether operations are destructive, overwrite existing content, or any side effects. Return value is not mentioned.

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 extremely concise (two sentences), front-loaded with the main purpose, and includes essential mode explanations without unnecessary detail.

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 no annotations and no output schema, the description could be more complete. It covers modes and axis defaults well, but does not explain pixel format, color specification, or behavior with frame/layer parameters.

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?

With 0% schema description coverage, the description adds value for mode, axis_x, and axis_y by explaining their behavior. However, parameters like pixels, color, filename, frame, and layer lack explanation beyond the schema.

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 the tool plots pixels with mirror images, distinguishing it from sibling tools like draw_pixels and mirror_layer. It explains the symmetrical modes (horizontal, vertical, both) and axis defaults.

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 implies usage for drawing symmetric patterns but does not explicitly state when to use this tool versus alternatives like draw_pixels or mirror_layer. No exclusions or context provided.

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