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

readOnlyHint=true already establishes this is a safe read. The description adds only the status vocabulary of returned records (pending, accepted, rejected), which is modest added value. It says nothing about pagination behavior, ordering, or result limits despite the tool exposing pageSize/pageNumber.

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?

A single front-loaded sentence with the verb and scoped resource up front and no filler. It is efficient, though brevity here shades into under-specification rather than true economy.

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 paginated list tool with no output schema and two undocumented parameters, the description leaves out pagination semantics, ordering, and the shape of results. An agent cannot tell whether it must page through results or what the statuses mean in terms of filtering.

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?

Two parameters (pageSize, pageNumber) exist with 0% schema description coverage, so the description is the only place meaning could be added. It mentions neither pagination nor the default page size of 50, leaving the parameters entirely unexplained. The parenthetical status list is not actually a parameter, so it doesn't compensate.

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 (List) and resource (invitations) with a clear scope: invitations the coach has sent to prospective clients. The parenthetical enumerates possible statuses, which sharpens what the resource is. It doesn't explicitly name or contrast with siblings like get_my_pending_org_invitations, but the 'coach has sent' framing implicitly separates it from received-invitation tools.

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?

No when-to-use guidance, no prerequisites, and no alternatives named. It never clarifies the relationship to get_my_pending_org_invitations, list_prospects, or list_organization_prospects, all of which live near this tool. The agent must infer usage purely from the resource noun.

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