list_images

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

No annotations exist; the description does not confirm read-only behavior, permissions, or side effects. While listing images is likely safe, the lack of explicit behavioral cues (e.g., 'This operation does not modify the sheet') leaves uncertainty.

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, well-constructed sentence that front-loads the core purpose. Every word contributes meaning, with no redundancy or unnecessary text.

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?

No output schema exists; the description mentions an index but does not specify output format or content. It lacks details on error conditions or handling missing sheets. Functional but minimally complete for an agent to rely on.

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 coverage, the description should explain parameters. It vaguely mentions 'in a sheet' but does not define the role of session_id or how to specify the sheet. The agent must guess that session_id identifies the workbook session.

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 verb 'list' and the resource 'pictures embedded in a sheet', and explicitly ties it to the sibling tool 'delete_image' by mentioning the index, making its purpose and differentiation from other list tools evident.

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 before delete_image but does not explicitly state when to use or avoid this tool, nor does it compare with alternatives among siblings like list_charts. No exclusion criteria or context for selection are provided.

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