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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds modest value by disclosing the return fields (email, role, invitation date), but it does not clarify behaviors like whether expired or already-accepted invitations are included, or pagination. No contradiction with 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?

A single, front-loaded sentence with no filler. It efficiently covers action, resource, scope, and return fields. It could carry slightly more guidance without bloat, but it is appropriately sized for a simple listing operation.

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 low-complexity, read-only tool with one parameter and full annotation coverage, the description is nearly complete: it states the resource, scope, and return values. Minor gaps include no mention of pagination/limits and no lifecycle context linking to invite_member or revoke_invitation, but these are not critical for correct invocation.

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 0%, so the description must compensate. 'For a workspace' weakly contextualizes workspaceId, but it does not explain what a workspaceId is, how to discover it, or its format. The single parameter's name is self-explanatory, but the description adds barely more meaning than the schema already provides.

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 states a specific verb ('List'), a specific resource ('pending invitations for a workspace'), and discloses the return fields (email, role, invitation date). This is clear and unambiguous, but it does not explicitly name or differentiate from siblings such as campaignstack_list_members or campaignstack_invite_member, leaving distinction to inference.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention that this complements invite_member/revoke_invitation or how it differs from list_members, so an agent must infer the appropriate context from the tool name alone.

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