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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds behavior annotations cannot express: the cursor-chaining loop, the done:true termination signal, and the fact that top search queries are null when Search Console isn't synced. That null-handling caveat and the loop mechanics are exactly the kind of context that prevents an agent from stalling or misreading an empty field.

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?

It is dense and somewhat long, but every sentence carries load: loop scope first, payload contents next, workflow, termination, then the large-catalog alternative. Front-loading the tool's identity before the workflow detail keeps it easy to scan despite the length.

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?

An output schema exists, so return values need not be explained, yet the description still characterizes the payload well enough to be actionable. Combined with the workflow, termination signal, and large-catalog escape hatch, nothing an agent needs to drive this loop correctly 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 schema already documents cursor provenance, the feedId default, and the full section enum. The description reinforces cursor chaining ('call this again with the returned cursor') and the section walk but adds no syntax or format detail beyond the schema, so the baseline of 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?

The description states a specific verb and resource ('Returns the next product needing work in a section') and explicitly frames the tool as the one-product-at-a-time loop, which immediately distinguishes it from the batch-oriented siblings. It names the exact payload the call returns, so an agent knows precisely what this tool yields versus what list_section_products yields.

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?

It gives explicit when-to-use conditions ('for small catalogs and for the exceptions left after a field-wide fix') and an explicit when-not with the named alternative ('On a large catalog, prefer list_section_products plus one update_feed_settings change over hundreds of overrides'). It also lays out the full surrounding workflow with the sibling tools to call between iterations.

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