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

The description adds significant behavioral context beyond the annotations: it warns that this is a sensitive read returning confidential data, that it is read-only but not harmless, and that expired invites are deliberately included. It also explains the server-computed status semantics, which annotations do not cover. No contradictions with annotations found.

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?

The description is dense but every sentence earns its place—it covers core behavior, exceptions, sensitivity, pagination, and related actions without redundancy. The most important scoping constraint is front-loaded, and the structure flows logically from function to usage to warnings.

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 no output schema, the description provides the return structure ({ result, nextCursor, prevCursor }), the id format, pagination mechanics, and sensitivity warnings. It also explains the meaning of expired status and the relationship to delete/create. Nothing 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?

Although the schema already documents both parameters (limit and cursor) at 100% coverage, the description adds crucial meaning: it explains the camelCase vs REST naming, how to page by sending nextCursor back as cursor, and that larger limit values are clamped. This goes beyond the schema's basic descriptions and enriches the semantics.

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 clearly states the tool lists organization invitations that have not been redeemed or withdrawn, and explicitly distinguishes itself from siblings like member.list and invite.delete/create. It gives a precise verb, resource, and scope, leaving no ambiguity about what the tool returns.

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 explicitly says when to use this tool (for pending/expired invites) and when not to (for people who already joined, use member.list). It also clarifies that resending the same invitation is a human action with no AI equivalent, and explains pagination usage with nextCursor. This provides comprehensive routing guidance.

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