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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful behavior beyond that: page-based pagination via ijn and the exact shape of each returned image record. It omits operational caveats such as auth requirements, rate limits, or scraping failure modes, which keeps it from a 5.

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?

Purpose is front-loaded in the first sentence, followed by capability detail and use cases. Both sentences carry information, though the multi-item use-case list is the most expendable element and could be trimmed without losing call-relevant guidance.

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 an 11-parameter, single-required-argument scraper with no output schema, the description usefully summarizes the return record fields (title, source URL, image URL, thumbnail, dimensions, source name, position) and pagination. That covers the main gap left by the absent output schema; remaining gaps are operational rather than structural.

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 description coverage is 100%, so the schema already carries full parameter documentation (including the exhaustive tbs filter syntax and enum values). The description's summary of filter categories and pagination maps onto parameters already documented and adds no syntax or default details, so the baseline 3 is appropriate.

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?

Opens with a specific verb+resource ('Get Image Search Results', 'Scrapes Google Images for a query') and enumerates both the filter dimensions and the returned fields. An agent knows exactly what operation this performs without opening the schema.

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?

Provides a concrete list of intended scenarios ('visual-asset discovery, reverse-image workflows, dataset collection for ML/CV training, brand/logo monitoring, stock-image sourcing'), which gives clear context for when to reach for it. It stops short of stating exclusions or prerequisites, and there are no sibling tools to route against.

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