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

Annotations already declare readOnlyHint true, so safety is covered; the description adds real context beyond that – access restriction, newest-first ordering, status values, and email masking as first-letter/domain. It does not cover pagination or response shape, keeping it at 4.

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?

Content is front-loaded and each clause earns its place (statuses, ordering, email masking, use case). The opening fragment 'Owner, or a member allowed to invite.' is slightly abrupt and reads as an access note, but overall the text is efficient.

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 read-only tool with no output schema, the description conveys return content (statuses, who joined when, masked emails), ordering, and access prerequisites. Very little an agent needs to call it correctly is missing.

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 coverage is 100%, so both parameters (api_token, workspace_id) are fully documented in the schema. The description implies the workspace scope but adds no syntax or format detail beyond what the schema provides, so 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?

States a specific verb and resource ('This workspace's invites') with clear scope and content enumeration (pending, joined, expired), which lets an agent distinguish it from create_invite / invite_by_email. It does not explicitly name sibling alternatives, so a 4 rather than 5.

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?

Explicitly gives the use case: 'Use it to see whether someone you invited joined, or whether their invite ran out and needs resending.' It also states the access requirement (owner or member allowed to invite), giving clear context without naming exclusions or alternative tools.

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