create_team_invitations

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

With no annotations provided, the description must carry the transparency burden. It only states the basic creation action without disclosing side effects like whether emails are sent, invitation expiration, duplicate handling, or permission requirements. This leaves room for potentially surprising behavior.

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 a single, clear sentence with no redundant words. It front-loads the action and target, making it easy to parse. Nothing extraneous is included.

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 simple creation tool, the description covers the core functionality but lacks important context. There is no output schema, so the description could mention return values or success behavior, but it does not. It also omits constraints like whether invitations require sending email or have limits. This is minimally complete but has 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 coverage is 100% with descriptions for all three parameters, so the baseline is 3. The description's 'one or more email addresses' reinforces the emails parameter but adds no new meaning beyond the schema. Role and teamId are not elaborated in the description.

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: creating invitations for one or more email addresses to join a team. It uses a specific verb ('create') and identifies the resource ('team invitations') plus the target (email addresses). This distinguishes it from sibling tools like get_team_invitations or delete_team_invitation.

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 provides no guidance on when to use this tool versus alternatives such as adding members directly or updating existing invitations. Sibling tools suggest a broader team management workflow, but the description does not mention any exclusions, prerequisites, or conditions for use.

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