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

Annotations already indicate this is a non-readonly, non-idempotent, non-destructive operation. The description adds useful behavioral constraints about required roles and role hierarchy, but it does not disclose other side effects such as whether an invitation email is sent or whether the invite creates a pending state. The sendEmail/frontendUrl schema descriptions cover email behavior partially.

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 concise sentences with no fluff. The core purpose is front-loaded, and the permission constraints follow naturally without redundancy.

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?

The description covers the essential decision factors: what the tool does, who can use it, and a key role constraint. With no output schema, it could have mentioned the result or side effects more explicitly, but the combination of description and schema provides enough context for correct invocation in most cases.

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 50%, but the tool description adds meaning by clarifying that teamId is optional and by explaining role hierarchy constraints ('You cannot grant a role higher than your own'). The sendEmail and frontendUrl parameters already have detailed schema descriptions, so the description compensates reasonably for the params that lack schema documentation.

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 clearly states the action ('Invite a person') and the resource (an organization you administer), plus the optional team assignment. It is specific enough to identify the tool's purpose, though it does not explicitly differentiate from sibling invite tools like createTeamInvite or bulkCreateTeamInvites.

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 context for when to use the tool: inviting someone to an organization the caller administers. It also provides crucial permission guidance by stating the required roles and the restriction that you cannot grant a role higher than your own, though it does not discuss alternatives or exclusions.

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