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

Annotations only declare readOnlyHint=false, so the description must carry behavioral weight; it does disclose the confirm-gated preview behavior, which is genuinely valuable. It omits permission requirements, whether an email is dispatched immediately on confirm, and what the preview contains.

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 compact sentences with the core action front-loaded and the confirm gate appended where it is needed. No filler, though the role list in parentheses is slightly terse given organizationRole has more values.

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 mutation tool with sparse annotations, no output schema, and a nested input object at 50% coverage, the description covers the main action and the confirm gate but not the invite lifecycle (email delivery, expiry, preview contents) or sibling disambiguation.

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 50%: organizationId and confirm are self-documented, while email, locationId, locationRole, organizationRole, and expiresInHours are not. The description adds the role vocabulary (admin/primary coach/coach) and the optional location, but leaves expiresInHours and the OWNER organizationRole value unexplained.

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 staff member ... to a gym by email') and names the roles and optional location scoping. However, it does not distinguish itself from close siblings like invite_coach_to_organization or invite_imported_gym_member, leaving the agent to infer which invite tool applies.

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?

The parenthetical about confirm-gating implies a preview-then-execute workflow, which is useful usage context. But there is no explicit guidance on when to use this tool versus invite_coach_to_organization / invite_client_to_organization / send_invitation.

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