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

Annotations already flag destructive, non-idempotent, open-world behavior, and the description adds genuinely new behavioral facts: the link is single-use, bound to that address, expires in seven days, and replaces any earlier pending invitation to the same address. These are exactly the side-effect details an agent needs before mutating invite state.

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?

Three short, front-loaded sentences. The core action comes first, followed by the two facts (single-use/seven-day link, prior invitation replaced) that matter most. 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 3-parameter mutation tool with full annotation coverage and no output schema, the description covers the important side effects well. It is slightly thin on prerequisites (who may invite, what happens on failure or to an existing teammate with that address) but nothing essential to calling it correctly is missing.

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 100%, so role enum meanings, email, and the two-phase confirm workflow are already fully documented in the schema. The description only echoes the 'with a role' concept and adds no parameter detail beyond it, which is the baseline case.

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 ('Email someone an invitation to join the workspace with a role') and the lifecycle detail about replacement helps separate it from resend_invitation. It does not explicitly name the closest siblings (resend_invitation, revoke_invitation, change_teammate_role), so it falls short of full sibling 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 invitation lifecycle described, but there is no explicit when-to-use or when-not-to-use guidance and no routing to the alternatives in the sibling list (resend_invitation for an existing invite, revoke_invitation to cancel). The confirm workflow guidance lives in the schema, not the description.

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