image

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

With no annotations, the description carries the full burden and does well: it discloses that the no-region path returns a lettered grid plus EXIF, palette, and OCR-with-grid-cells, and that region requests return a native-resolution crop enlarged when small. It omits operational limits like max file size, auth, or whether source accepts data URIs/base64, leaving some behavioral gaps.

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 definition is front-loaded ('One image (file or URL)') and then cleanly splits the two modes with 'Without region...' / 'With region...'. Every clause contributes either coordinate format, output content, or usage rationale, with no filler.

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 2-parameter, no-output-schema, no-annotation tool, the description covers both input semantics and the shape of returned content in each mode, which is most of what an agent needs. Minor gaps remain around source formats (data URI vs. path vs. URL) and image size limits.

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%, so the description must compensate, and it does: it spells out accepted region syntaxes ('B2', 'B2:C3', 'x,y,w,h' in px or 0-1 fractions) and defines the default behavior when region is omitted. It also clarifies that source is a file or URL, giving meaning to both parameters beyond the 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?

The description names a specific resource ('One image (file or URL)') and clearly delineates two operating modes: overview with a lettered grid + EXIF/palette/OCR, and native-resolution region extraction. It differentiates itself behaviorally (region zoom vs. full overview) but never explicitly contrasts against near-name siblings like 'images', 'zoom', or 'look'.

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?

It gives a clear use case: 'Use it to read small text in big screenshots and photos instead of guessing,' which tells the agent when this tool is the right pick. It does not name alternative siblings (e.g., 'zoom', 'look') or state when not to use it, so the guidance stops short of explicit routing.

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