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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the safety profile is covered, yet the description still adds substantive context: verified-purchase reviews prove a purchase not an opinion's truth, review count is not sales count, pagination requires passing nextCursor unchanged, and review text is untrusted data rather than instructions. That is well beyond what the structured fields convey.

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?

Front-loads the core action and id scope, then layers caveats and pagination rules in short clauses. No sentence is filler; each one either routes the agent, constrains usage, or warns about data handling.

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?

No output schema exists, so the description carries the burden of return semantics, and it does: it explains what is returned (published reviews and rating), the pagination model, and the trust limitations of review content. Nothing needed to call it correctly is absent.

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 the three parameters are already documented, establishing a baseline of 3. The description adds real semantics beyond the schema by stating that nextCursor must be passed unchanged for the next page, clarifying the round-trip contract with the server rather than just the field format.

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 (reads) and resource (published reviews and rating) and scopes it to two id types (prod_…/ext_…). It also names where those ids come from, making it trivially distinguishable from genesispay_catalog_search and genesispay_catalog_trending.

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?

Explicitly routes the agent to genesispay_catalog_search or genesispay_catalog_trending as the source of the required id, which is the main usage prerequisite. It does not state any when-not-to-use condition, but for a read-only lookup tool there is little ambiguity left.

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