image_pages_overview

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

No annotations are provided, so the description carries the full burden. It does not disclose that the tool is read-only (safe to invoke without side effects), nor does it mention any rate limits, authentication needs, or whether results are cached. The presentation instructions are about output formatting, not behavioral traits.

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 functional description is concise (first 3 sentences). However, the lengthy presentation guidelines (5 sentences) add significant bloat that could be a separate instruction. The description earns its place for the core purpose but wastes space on output formatting details that are not about the tool's behavior.

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 tool with 4 parameters and 25+ siblings, the description lacks completeness. It does not explain what data is returned (no output schema), how the results are structured, whether pagination is supported, or how it differs from similar image tools like image_impressions_no_clicks. The presentation instructions are unnecessary for contextual completeness.

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 documents all 4 parameters. The description adds no extra meaning beyond the schema (e.g., does not explain how min_impressions relates to 'which pages are surfacing' or what position sorting means in this context). Baseline 3 is appropriate since the schema does the heavy lifting.

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 this tool ranks pages by image-search performance, distinguishing it from siblings like image_keyword_overview (which maps ranking queries to pages). The verb 'ranked' and the specific resource 'pages on the site by image-search performance' make the purpose explicit and unique.

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?

The description implies use when analyzing which pages surface in Google Images vs. which do not, and pairs it with image_keyword_overview. However, it does not explicitly state when not to use this tool or provide alternatives among the many sibling tools (e.g., image_impressions_no_clicks, image_content_decay) for different use cases.

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