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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real context beyond them: it discloses the ordering (newest first), the scope restriction to pending+accepted invitations, and that 'total' represents the invitation count. It does not discuss rate limits or result caps beyond limit's max, but for a read-only list this is solid.

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 dense sentences with zero waste; the primary purpose and returned-field list come first, followed by pagination and the revoke cross-reference. Efficient, though the field enumeration makes it slightly long.

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?

With no output schema, the description properly compensates by naming the returned fields and the meaning of 'total', which is exactly what an agent needs. Ordering and pagination are covered; nothing critical for correct invocation is missing, though a note on default page size or edge cases would push it higher.

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 id, limit, and offset are already fully documented, making 3 the baseline. The description restates pagination semantics and clarifies that 'total' is the invitation count (a return concept, not a parameter), adding only marginal value beyond the schema.

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 precise verb+resource ('List a Clarity process's pending and accepted invitations') and enumerates the exact fields returned (accepted status, account-free link sent, link opened, interview submitted). An agent can distinguish this from sibling list tools like listTeamInvites or listClarityTeamInterviews at a glance.

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?

Gives clear operational context (newest-first, paginate with limit/offset) and explicitly routes a related action — revoking a pending invitation — to deleteTeamInvite. It lacks an explicit statement of when NOT to use it or which sibling list tools it replaces, so it stops short of a 5.

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