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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety bar is low; the description still adds substantive behavior: cursor pinning to the first page's publication/package, stale_product_cursor on listing change, short pages, null next_cursor on the last page, and the two error codes. It even flags that file names and paths are untrusted seller text, which no annotation covers.

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 and each sentence carries a distinct fact: alternative, cursor pinning, paging edge case, error codes, injection warning. It is dense but not padded; the injection sentence is long but justified for a tool returning seller-authored strings.

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?

With an output schema already covering return shape, the description fills the remaining gaps an agent needs: pagination termination, cursor scoping invariant, the two failure modes, and the trust boundary on returned text. Nothing material to a correct call 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 coverage is 100%, so baseline is 3; the description earns above that by explaining that a page may return fewer than limit files and that next_cursor is null on the last page, which is how an agent should interpret these params in practice. It also supplies the correct reaction to a stale cursor rather than leaving it to the schema.

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?

States a specific verb and resource: paging through the manifest of the package a buyer currently receives for one product. It explicitly contrasts with get_product_readme (setup/usage text), so an agent can pick between the two siblings without opening either 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?

Names the triggering condition ('when a recommendation depends on the package manifest') and routes the alternative case to get_product_readme by name. It also says what to do when the cursor goes stale: restart without a cursor.

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