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

Annotations already declare this a safe, idempotent, closed-world read, so the description's burden is lower. Beyond that it adds only 'Pending', with no mention of scoping, pagination, ordering, or what happens when the optional organizationId is omitted.

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?

Two words are technically concise, but the dimension rewards appropriately sized and front-loaded information. This is under-specification rather than economy: the one useful qualifier ('Pending') is not developed into anything an agent can act on.

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 list tool with an optional org parameter and no output schema, the description should at least clarify scope, pending definition, and whether results are paginated. It supplies none of these, leaving the agent to infer behavior from the name and annotations alone.

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% and the single parameter is documented as an approved workspace id, so the schema already carries this information. The description contributes nothing about the parameter, which is acceptable at baseline but not additive.

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 is essentially a restatement of the name and title ('list_invites' / 'List invites'), adding only the status qualifier 'Pending'. It does not state a verb or clarify what an invite record contains, and it does nothing to distinguish this from siblings such as list_members or revoke_invite.

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 versus related tools like accept_invitation, revoke_invite, or invite_member. The word 'Pending' implies a filter but the description never says whether it lists only the caller's invites, a workspace's invites, or when to use it at all.

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