ImageSearch

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

Discloses backend behavior (Brave vs DuckDuckGo) and safesearch parameter effects. With no annotations, provides moderate transparency but lacks details on rate limits, permissions, or edge cases.

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?

Concise at 3-4 sentences, well-structured, front-loaded with main action. Slightly verbose on backend details but overall efficient.

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?

Covers return data, optional download, and safesearch. Lacks output schema, but description sufficiently explains returned fields. Completeness is good for a search tool.

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?

Adds meaning beyond schema: explains backends, safesearch options in context, and clarifies fetch_top_n downloads locally. Schema coverage is 100%, so baseline is 3; description provides extra value.

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?

Description clearly states 'Search for images' and details return types (URLs, thumbnails, dimensions) and optional local download. Distinct from sibling tools (PaperFetch, WebFetch, etc.) which are not image-specific.

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 explicit guidance on when to use this tool versus alternatives. Does not mention when not to use or prerequisites.

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