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

Annotations already mark this as a non-read-only, open-world, idempotent, destructive-capable mutation, and the description adds useful context: an invitation email is sent, the caller must be an owner, explicit user request is required, and plan seat limits apply. It could say more about the destructive/seat-consuming effect and idempotency behavior, but it adds real value beyond the 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?

The description is three short, front-loaded sentences with no wasted text. Owner-only scope, action, side effect, consent condition, and seat limit are all stated efficiently.

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 two-parameter mutation with annotations and no output schema, the description covers the key operational concerns: authorization, side effect, explicit-use requirement, and seat limits. The remaining idempotency detail is already handled by the request_id schema description.

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%: email has format and pattern validation but no prose description, while request_id has a clear idempotency description. The description clarifies the email parameter's purpose (invite by email) but does not add meaning for request_id beyond the schema.

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 uses a specific verb and resource — inviting a team member by email — and adds the owner-only scope. It clearly distinguishes this action from sibling tools such as cancel_team_invitation and remove_team_member.

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?

It explicitly says to use this only when the user explicitly asks, and it notes the owner-only restriction. It does not name alternative tools or explain when to choose cancellation/removal instead, so it falls short of full when/when-not/alternatives guidance.

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