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

The description adds meaningful behavioral context beyond the annotations: it discloses an auth requirement and explicitly rules out side effects like sending email or accepting membership. This is valuable reassurance for an invitation-related tool and does not contradict any annotation.

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 tight sentences: the first front-loads the operation and return contents, the second covers permission and side-effect safety. Every clause 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 paginated list tool with rich annotations, the description covers what is returned, who may call it, and what side effects will not occur. The pagination parameters are fully constrained in the schema, so nothing critical 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?

The input schema defines limit and offset with defaults and bounds, but the description provides no guidance on how pagination affects the returned invitation list. With 0% schema description coverage, the description was expected to compensate, and it does not.

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 names a specific verb ('List'), a specific resource ('workspace invitations'), and a clear scope ('current and historical'). It also specifies the returned attributes (recipient, role, revision, delivery/acceptance state), making it easy to distinguish from sibling tools like send_workspace_invitation or revoke_workspace_invitation.

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?

It clearly states the access restriction ('Owner/admin only') and reassures that reading never sends email or accepts membership. It does not explicitly name alternatives or exclusion criteria, but the listing purpose and sibling names make the intended use reasonably clear.

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