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

The annotations already declare readOnlyHint=true, so the description correctly aligns with a read operation. It adds useful context by specifying that only 'pending' invites are shown and that they are scoped to the organization. However, it discloses nothing about pagination defaults, ordering, or authorization, so it is just adequate beyond the annotations.

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?

The description is a single informative sentence plus an endpoint reference, with no filler. It is front-loaded with the core action and resource, making it easy to scan and every word earns its place.

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?

For a simple read-only list operation, the description plus schema and annotations cover what an agent needs: the resource, the pending filter, the pagination parameters, and the safety profile. Without an output schema, no return-shape detail is required, and there are no complex behaviors left undocumented.

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?

The input schema fully documents both parameters (page_size and current_page) with defaults and descriptions, giving 100% schema coverage. The description itself adds no parameter-specific meaning, so it relies entirely on the schema, matching the baseline score.

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 clearly states a specific action ('List'), a specific resource ('pending user invitations'), and scope ('to the organization'), and it names the exact endpoint. This distinguishes it from sibling tools like portkey_list_users, which target existing users rather than 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 resource name and intent ('List pending user invitations') imply when to use it, but there is no explicit guidance about when not to use it or which sibling tool should be chosen for similar needs. It neither mentions alternatives nor exclusion criteria, so usage context must be inferred.

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