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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the phrase 'pending / accepted state', and it is ambiguous whether that means results are filtered by state or simply include a state field, which is the one behavioral point that actually needed disambiguation.

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?

It is a single short fragment with no filler, and the distinguishing detail (invitation state) comes first. However it is a sentence fragment without a verb, so it reads as a label rather than a statement of action.

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 zero-parameter read tool with rich annotations and no output schema, most of what an agent needs is already structured. Still, the description never clarifies whether the result set is scoped to the current workspace or whether pending and accepted invitations are returned together, which is exactly the kind of thing this short description should settle.

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 tool takes zero parameters, so there is no parameter semantics for the description to compensate for. Baseline 4 applies to parameterless tools.

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 text 'Workspace invitations with pending / accepted state' names the resource and hints at a state dimension, but supplies no verb, so the listing action is only inferable from the tool name. It also does not distinguish itself from the nearby list_workspace_members or list_workspace_roles siblings.

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?

There is no guidance on when to call this rather than any sibling, and no prerequisites or scoping conditions are mentioned. The agent must infer from the name that this is the tool for enumerating invitations.

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