list_images

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to reiterate safety. It adds value by specifying the return type ('a list of image attrs dicts') and explaining the parameters' effects. This is sufficient for a simple read-only listing tool.

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 very concise and well-structured with 'args:' and 'returns:' sections. It uses minimal but informative language, with no unnecessary words or repetition.

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?

The description covers the core functionality of listing images and the parameters. It explains the return type. However, it does not mention whether all images are listed by default (implied by no required params) or address pagination or ordering, which could be relevant for large numbers of images.

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?

Despite 0% schema description coverage, the description provides clear, concise explanations for all three parameters: name, all, and filters. For filters, it even lists example attributes (label, dangling, before, since, etc.), which goes beyond the schema's type-only information.

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 'List images' and the resource 'on the server'. It explains the optional filtering parameters, making the purpose unambiguous. However, it does not explicitly distinguish itself from the sibling 'search_images' tool, which might serve a similar function.

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 provides no guidance on when to use this tool versus alternatives. It does not mention situations where list_images is appropriate, nor does it reference other tools like search_images for more advanced filtering.

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