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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the concrete endpoint (GET /merchant/invitations) and enumerates the returned fields, which is useful, but says nothing about auth, rate limits, sorting, or pagination metadata beyond the parameter names.

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 front-loaded sentence covers resource, returned fields, filters, and paging, followed by the endpoint. Dense and near-waste-free, though the parenthetical field list is slightly listy.

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 no output schema, the description compensates by naming the returned fields, and annotations cover the safety profile, leaving little the agent needs before calling it. Minor gaps around response structure and defaults (page default is in the schema) keep it from a 5.

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 all four parameters are already documented in the schema (including the true/false semantics of invite_sent). The description restates order id, sent state, and page/limit without adding format or range detail beyond what the schema provides, so the baseline 3 applies.

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?

Names the specific resource (company review invitations), its scope (queued or sent), and the fields returned (customer, order, send date, status), which clearly separates it from the sibling list_product_invitations. It does not explicitly name that sibling, so it stops short of a 5, but an agent can identify the tool's remit without opening the 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?

Gives clear operational context: filter by order id or sent state, and page with page/limit. It does not state when to prefer the product-invitation sibling or any exclusions, so it lacks the explicit when-not routing of a 5.

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