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

With no annotations, the description carries the full burden, and it does disclose two important traits: the confirm gate and the fact that a real email is dispatched to the recipient. It omits other meaningful behavior a caller needs — required permission/role level, that the invite can expire, and whether re-inviting the same email is idempotent or duplicative.

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 tight sentence with the action front-loaded and the two caveats (confirm gate, real email) appended where they matter. 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?

For a 6-parameter mutation with no annotations, no output schema, and low schema coverage, the description is only partially sufficient. It covers the confirm gate and the external email side effect but leaves role semantics, the expiry parameter, and permission requirements 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 coverage is only 17% (just the 'confirm' param documented), so the description must compensate. It does name email, role, optional location, and the confirm gate — four of six parameters — but never explains the role enum values (OWNER/ADMIN/PRIMARY_COACH/COACH) or the expiresInHours control, leaving meaningful gaps.

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 states a specific verb and resource ('Invite a coach to join the organization') plus the key input dimensions (email, role, optional location), so the action is unambiguous. It does not explicitly contrast with near-neighbors such as invite_client_to_organization or send_invitation, but the name carries that differentiation.

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?

Usage is implied by the action statement, and the '(confirm-gated)' and 'They receive a real email' notes hint that this has outward-facing consequences worth pausing over. However, there is no explicit when-to-use versus when-not, no prerequisite/permission conditions, and no pointer to the client-invite sibling.

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