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

No annotations exist, so the description carries the full burden. It does usefully disclose two behavioral facts: the operation is confirm-gated (preview mode) and it sends 'a real email' as an external side effect. However, it omits permissions/role requirements, what happens on duplicate invitations, and expiry behavior, leaving significant gaps for a mutation tool.

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 tight sentences, front-loaded with the core action and followed by the behavioral punchline. No filler; every clause carries information about scope, optionality, or side effects.

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?

A 6-parameter mutation tool with no annotations and no output schema ideally needs more coverage. The description handles the side effect and confirmation well but leaves expiresInHours unexplained and says nothing about permission requirements or failure conditions, so it is only minimally complete.

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 only 17% (just the 'confirm' param), so the description must compensate. It adds meaning for coachId and locationId ('pre-assigned to a coach and location') and confirms the confirm-gating, but never explains the required organizationId semantics or the expiresInHours parameter at all, leaving two parameters undocumented.

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 ('Invite a client to join the organization by email') plus its optional pre-assignments. The word 'client' implicitly separates it from the sibling invite_coach_to_organization, though it never names that alternative explicitly.

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 phrasing, but there is no when-to-use/when-not guidance. With siblings like send_invitation, create_prospect, and invite_coach_to_organization in the same namespace, the description gives no signal for choosing between them.

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