get_pixels_rect

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

No annotations provided; description adds return format (JSON array of pixel objects) but omits potential performance considerations for large regions or coordinate system details. Still provides substantial behavioral context.

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?

Well-structured docstring with Args and Returns sections, front-loaded with purpose. Could be slightly more concise but clear as is.

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?

Covers all parameters and return format. Lacks details on coordinate origin, bounds checking, or maximum region size. For a read operation with no output schema, it is reasonably complete but could add more context.

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%, but description explains all 7 parameters, including defaults and meaning (e.g., 'uses active layer when empty' for layer_name, 'starting at 1' for frame_index). Adds significant value beyond bare 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?

Description clearly states 'Read all pixel colors in a rectangular region' with specific verb and resource, distinguishing it from siblings like get_pixel_color (single pixel) and draw_rectangle (drawing).

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 vs alternatives. Implies use for reading a rectangular region of pixels, but lacks context on performance tradeoffs or when to prefer over get_pixel_color.

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