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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond that: the owner/admin authorization requirement and the pending-only filter, plus the explicit exclusion of join links. It does not mention pagination or result limits, which is the only meaningful gap.

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 sentences, front-loaded with the core action and scope, followed by prerequisites and sibling routing. Every clause earns its place — the field list, the role requirement, and the exclusion all carry information.

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?

There is no output schema, and the description compensates by naming the returned fields (invitee, role, expiry). Combined with the auth requirement and the pending-only scope, an agent has enough to call it correctly. Only pagination/result-size behavior is unaddressed.

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%, so both parameters are already fully documented in the schema, including the in_workspace vs workspace_id distinction. The description restates the workspace_id default ('or one named by workspace_id') but adds no syntax or behavior beyond the schema. Baseline 3 applies when the schema carries the load.

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?

Specific verb+resource+scope: 'List the invitations ... that are still pending' on the active or named workspace. It pre-empts confusion with sibling tools by stating join links are not returned and pointing to workspace_invite_revoke / workspace_invite for those actions.

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?

States the prerequisite ('Requires owner or admin role'), the default target ('active workspace (or one named by workspace_id)'), and routes follow-up actions to the correct siblings for revoking or re-sending invites. An agent knows both when to call this and what to call instead for related operations.

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