Get Best Image

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

No annotations are provided, so the description must fully disclose behavior. 'Best image' is vague—it doesn't explain how 'best' is determined, what happens when no match exists, or the output format. The description adds only the bare minimum that a single image is returned.

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 short sentence, making it extremely concise and front-loaded. However, it's so sparse that it omits valuable context that could be added without bloating the description, like criteria for 'best' or relationship to sibling tools.

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 the tool's simplicity and the absence of an output schema, the description is functionally thin. It doesn't address key contextual elements like disambiguation from other search tools or behavioral edge cases, making it incomplete for a new agent.

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?

The input schema covers both parameters with descriptions, so baseline is 3. The tool description doesn't add any meaning beyond the schema, merely echoing the notion of a query and not mentioning orientation. Since schema coverage is 100%, no penalty, but no added value either.

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 uses a specific verb 'Return' and identifies the resource 'best image' with a query scope, making it clear what the tool does. However, it doesn't explicitly distinguish from sibling tools like search_images, which may also return images, beyond the 'single best' phrasing.

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?

There is no guidance on when to use this tool versus alternatives like search_images or search_images_batch. The description only states the mechanical function, with no context about selection criteria or expected use cases.

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