get_image_output

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

Given no annotations, the description discloses basic functionality and returns a list of images, but lacks details on side effects, authentication, or specific return format (e.g., base64 vs file paths).

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 succinct and well-structured with an Args and Returns section, front-loading the purpose with no unnecessary words.

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 simple tool with one parameter and no output schema, the description adequately covers purpose, parameter, and return type. It misses details on error conditions or image formats, but is largely complete.

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?

The description explains the single parameter 'index' as 'the index of the cell to get images from', adding meaning beyond the schema's type and title, which is valuable since schema coverage is 0%.

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 action 'Get image outputs' and the resource 'from a specific cell by its index', distinguishing it from siblings like get_cell_text_output which retrieves text.

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 when needing images from a cell, but provides no explicit guidance on when to use this tool over alternatives, such as when text outputs are needed instead.

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