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

Annotations already declare destructiveHint=false and openWorldHint=true, so the external-email side effect is partly covered. The description adds genuinely new behavioral context: the tool must only run after explicit user confirmation, which is a hard gating constraint not expressible in the annotation set.

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 front-loaded sentence with no filler; the action, the object, and the gating condition all appear immediately and every word earns its place.

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?

An output schema exists, so return values need not be explained, and the annotations cover the safety profile. Still, for a four-parameter, fully-required mutation tool with 0% parameter coverage, the description omits permission requirements and duplicate-invite behavior, leaving real gaps.

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 0% and none of the four parameters are described in the schema, so the description carries the full burden. It only loosely implies the meaning of 'confirmed' via 'explicit user confirmation' and says nothing about teamId, email, or the editor/viewer role enum, leaving most parameters undocumented in both places.

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 pair (create and email) and a specific resource (team invitation), which is enough to distinguish it from siblings like create_team or revoke_team_invite. It stops short of explicitly contrasting with those siblings, so it is clear but not sibling-differentiating.

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 phrase 'only after explicit user confirmation' is a real usage precondition and tells the agent when it may fire the tool. However, no alternatives are named and there is no guidance on when not to use it (e.g., versus create_team or revoke_team_invite), so usage is implied rather than fully specified.

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