get_composite_rect

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

With no annotations, the description carries the full burden of disclosing behavior. It indicates a read operation on visible flattened composite data, which is useful, but it does not explain coordinate space, how visibility/blending is resolved, frame handling, return structure, or any edge cases. For a read tool with no annotation safety profile, this is a meaningful gap.

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 sentence with no filler. It front-loads the operation and output type. It is concise without being purely tautological like 'Process', though it sacrifices useful detail for brevity.

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 6 parameters, no annotations, no output schema, and no usage guidance, this description is incomplete. An agent cannot determine what the returned JSON contains, how coordinates map to the visible composite, or what 'flattened' includes. The tool likely needs clarification to be invoked correctly on the first try.

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 0%, and the description provides zero parameter-level detail. Although names like x, y, width, height, filename, and frame_index are somewhat self-explanatory, the description does not clarify their combined semantics, units, or how frame_index interacts with the composite region.

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 uses a specific verb ('Read') and identifies a clear resource ('visible flattened composite region') with an output format ('as JSON'). It conveys that it reads composited visible content rather than individual layers, which distinguishes it from siblings like get_pixels_rect or get_composite_pixel, though it does not explicitly name an alternative.

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 siblings such as get_pixels_rect, get_composite_pixel, or inspect_sprite_geometry. The phrase 'visible flattened composite' implies when composited output is needed, but the description does not state criteria, prerequisites, or exclusions.

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