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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that results are paginated, which is genuinely useful context, but says nothing about rate limits, result ordering, or cost. Adequate but not rich beyond the annotations.

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?

A single, front-loaded sentence with no filler or redundancy. Every word carries information and the key distinction (stored images vs daily archive) comes first.

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 low-complexity, optional-parameter list tool with no output schema, the description is minimally sufficient — it conveys what is listed and that pagination exists. It leaves unresolved the relationship to images_daily and images_search, which matters given the crowded sibling set.

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 100% — limit, scope, and cursor are all documented inline, including the cursor's 'keep query and scope unchanged' constraint. The description's mention of 'the daily archive' loosely maps to the scope=daily value but adds nothing the schema does not already say, so the baseline of 3 applies.

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 states a clear verb+resource: 'List stored images or the daily archive', and enumerates the two collections covered. It does not differentiate this tool from siblings such as images_search or images_daily, leaving overlap with the dedicated daily-archive tool ambiguous.

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?

Usage is only implied: listing/browsing with pagination suggests this is for enumeration rather than search, which vaguely points away from images_search. There is no explicit statement of when to use this versus images_search, images_daily, or images_get, and no mention of alternatives.

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