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

readOnlyHint and openWorldHint already declare this is a safe, non-destructive read against an external service, so the burden is light. The description adds the record shape (customer, order, send date, status) and the endpoint, but says nothing about pagination limits, total counts, or ordering, leaving the behavioral picture only partially filled in.

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?

A single dense sentence plus endpoint: the resource comes first, then the returned fields, then the filters, then paging. The parenthetical list is slightly cluttered, but every clause carries information and nothing is redundant filler.

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 a read-only list tool, no output schema, and full parameter coverage, the main remaining question is what comes back — and the description answers that by enumerating the record fields (customer, order, send date, status). Nothing essential is missing, though ordering/pagination behavior is left implicit.

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 every parameter is already documented, including the invite_sent boolean semantics. The description only restates the filter axes (SKU, order id, sent state, page/limit) without adding format or default details beyond the schema — the baseline 3 for schema-covered params.

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 the specific resource (product review invitations), the sub-populations covered (queued or sent), and the fields returned (customer, order, send date, status), plus the underlying endpoint GET /product/invitation. The 'product' qualifier cleanly separates it from the sibling reviewsio_list_company_invitations.

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 filter options (SKU, order id, sent state) imply how to narrow results, and 'page through with page/limit' implies paging usage, but there is no explicit when-to-use guidance or naming of the company-invitations alternative. An agent can infer context but must decide on its own when this tool is the right pick.

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