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

Adds real value beyond the annotations: the per-invitation hourly rate limit and the two-phase confirm flow ('first call returns a summary and a confirmToken; call again with confirmToken to proceed'), which is essential to invoking the tool correctly. It labels the operation destructive consistently with destructiveHint=true, but never explains what makes it destructive (an email is sent to a real recipient) or what failure modes exist. No contradiction with annotations.

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 tight sentences with no filler. The purpose and rate limit come first, and the non-obvious two-step confirmation requirement is front-loaded rather than buried.

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 with no output schema, the description covers what the first call returns (summary + confirmToken), the rate limit, and the pending-invite precondition. It stops short of describing the result of the confirming call or error cases such as an invite that is no longer pending.

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 67%: site and confirmToken are documented in the schema, but inviteId has no schema description. The description compensates by telling the agent where inviteId comes from (list_team) and reiterates the confirmToken contract, adding meaning the bare schema lacks.

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 ('Sends the invitation email again for a pending invite') and points at the sibling list_team as the source of the inviteId. It clearly scopes the action to an existing pending invite, though it never explicitly contrasts itself with invite_teammate or revoke_invite, which are the tools an agent would most likely confuse it with.

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 description gives clear triggering context ('a pending invite from list_team') and a hard constraint ('At most once per hour per invitation'), which tells the agent when the call will be accepted. It does not name alternative tools or state when not to use this one (e.g., for already-accepted or revoked invites).

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