search_images

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

No annotations provided, so description carries full burden. It discloses that the tool searches Docker Hub, returns full names, and cannot search GHCR. It does not mention rate limits or read-only nature, but these are less critical for a search 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?

Well-structured with clear sections, emoji for emphasis, and examples. Every sentence adds value, though the content could be slightly more concise without losing clarity.

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 that results include full image names. It covers the essential context for tool selection and usage. Missing details like pagination or result fields, but sufficient for typical use.

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 descriptions and defaults. The description adds value through concrete examples showing how queries are interpreted (e.g., 'radarr' finds linuxserver/radarr, hotio/radarr), which aids understanding beyond the schema.

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 it searches for container images by name, provides examples, and distinguishes from sibling tools like find_image and get_latest_image_tag. The emoji warning and explanation of when to use it make the purpose unambiguous.

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 guidance to 'USE THIS FIRST' when image path is unknown, and to use find_image or get_latest_image_tag after obtaining the full name. Also warns about GHCR's lack of search API, directing to alternative approaches.

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