List Images

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the description need not repeat safety. It does add 'with pagination,' but this is already implied by the page and limit schema fields. No additional behavioral context (e.g., return format, ordering defaults) is disclosed 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?

The description is a single, front-loaded sentence that states the core purpose without any filler. It is appropriately sized for a simple listing operation, and every word contributes to the meaning.

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 straightforward listing tool with comprehensive annotations and full schema coverage, the description is mostly sufficient. The main gap is the lack of disambiguation between list_images and search_images, and no explicit mention of the return format (though no output schema exists). Overall, the definition is adequate.

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 100% with descriptive entries for all six parameters (url, lang, page, sort, limit, direction). The description itself adds no parameter-level detail, but the schema already provides adequate meaning, so the baseline of 3 is appropriate.

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 images in the AltText.ai library, providing a specific verb and resource. However, it does not differentiate from sibling tools like search_images, leaving some ambiguity about the exact scope (list all vs. list filtered).

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 offers no guidance on when to use this tool versus alternatives such as search_images, get_image, or filter by URL. There are no explicit use-case conditions or exclusions, leaving the agent to infer when a plain list is appropriate.

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