find_images

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

No annotations were provided. The description only states the purpose but does not disclose behavioral traits such as read-only nature, rate limits, or side effects. For a search tool, basic transparency about its read-only behavior would be expected.

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 with no extraneous information. It efficiently conveys the core purpose without waste.

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 parameterless tool with an output schema, the description is largely complete. However, it could mention whether the results are all images or filterable. The presence of an output schema compensates for missing return value details.

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?

There are no parameters, so the input schema covers 100% of properties. The description adds no parameter semantics because there are none. Per guidelines, baseline is 3 for high schema coverage, and the description does not improve or detract.

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 identifies the action ('Find'), the resource ('available Multipass images'), and the purpose ('for launching new instances'). It distinguishes from sibling tools that deal with instances or snapshots. However, it could be more specific about the scope (e.g., 'all available' or 'searchable').

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?

No guidance is provided on when to use this tool versus siblings (e.g., list_instances, get_instance_info). The description does not mention context, prerequisites, or exclusions. With 30 sibling tools, explicit usage guidance is missing.

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