xlsx_images

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

Annotations already declare readOnlyHint=true, destructiveHint=false, etc. Description adds that it reads xl/media/* and xl/drawings/* directly and returns metadata only, not pixel data. No contradictions.

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 with a clear main statement, an example, and distinct usage sections. Slightly wordy but front-loaded and easy to follow.

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?

Given no output schema, the description adequately explains return values (format, size, sheet, anchor). Mentions local file requirement. Does not specify pagination or base64 encoding but schema covers limit and required field.

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% (no parameter descriptions). The description does not explain file_b64 (base64) or the options.limit and options.sheet parameters beyond the tool's general capability. Lacks parameter-specific guidance.

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 tool lists every embedded image in a local .xlsx file with format, size, sheet attribution, and anchor cell range. It distinguishes itself from siblings like xlsx_read (cell values) and xlsx_charts (charts-as-images).

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?

Explicit USE WHEN (cataloging visual assets, auditing, fingerprinting) and DO NOT USE WHEN (want pixels, need cell values) sections. Provides alternative tool xlsx_read for cell values.

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