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

Annotations already cover readOnly/idempotent/non-destructive. The description adds real behavioral context beyond them: login plus OWNER/ADMIN authorization requirement, a 50-per-page cap, and the default filtering semantics (only pending + unexpired unless status=ALL). Could be stronger on error/auth-failure behavior, but it is well above what the annotations alone convey.

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?

Bracketed sectioning (auth, chain, caveats) front-loads the permission gate and the key default gotcha. Every clause carries information; no filler.

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?

No output schema exists, yet the description characterizes the returned records (who invited whom, acceptance state, expiry) and documents pagination and filtering defaults, so an agent has everything needed to call and interpret it.

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 the baseline is 3. The description nonetheless adds meaning: it explains what status=PENDING vs ALL actually return and confirms nextCursor is the pagination mechanism, giving the agent semantics beyond the bare enum.

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 (list the org's sent named invites), plus scope: sent BY this organization, with a permission qualifier. This cleanly separates it from siblings like list_my_organization_invites (invites to me) and list_organization_members.

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 names the downstream sibling revoke_organization_member_invite(inviteId) and the composition chain that leads to it (status=PENDING → revoke one). Also states which status values select which records, so the agent knows when to use each mode.

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