Search galleries across pages

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior. The description adds meaningful behavioral detail beyond annotations: the 10-page budget, deduplication of gallery references, and the resume-cursor behavior on truncation. These are not present in the annotations and materially shape how an agent should use the 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?

The description is a single, information-dense sentence. It front-loads the core purpose, then adds the key behavioral constraints and return behavior without wasted words. Every clause earns its place.

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 presence of a detailed output schema, strong annotations, and 100% parameter schema coverage, the description covers the non-obvious contextual details: pagination limits, deduplication, cursor continuation, and metadata expansion avoidance. Nothing critical for correct invocation is missing.

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 baseline is 3. The description adds some context by explaining the 'page budget' and 'resume cursor', which maps to maxPages and next, but the parameter schemas already document those fields well. No significant gap requires the description to compensate.

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 a specific action ('Search'), resource ('galleries'), and scope ('up to 10 result pages'), while also naming distinctive behaviors: no metadata expansion, deduplication, and resume-cursor return. This distinguishes it from single-page search and metadata-focused sibling tools.

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 when to use the tool: for multi-page gallery searches with deduplication and cursor continuation. However, it never explicitly names alternatives such as eh_search_galleries or states when not to use this batch variant, leaving the routing decision somewhat inferred.

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