create_team_invite

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

No annotations are provided, so the description must fully disclose behavioral traits. It does not mention whether this requires special permissions, if an existing invite is revoked when a new one is generated, or any expiration behavior. The description only states what it returns.

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 very short and front-loaded with the main purpose. The second sentence adds value by stating the return values. However, it could be slightly more compact by merging the two sentences.

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?

With an output schema present, the description need not explain return values, but given the tool's simplicity (1 param) and the lack of annotations, the description is complete enough for a basic understanding but fails to provide important context like permissions and behavior of replacing existing invites.

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 100%, so the schema already documents the single parameter (team_id) with a clear description. The description adds no extra meaning beyond what the schema provides, warranting a baseline 3.

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 (Generate a team join invite) and the resource (team invite link). It returns a token and inviteLink, distinguishing itself from sibling tools like create_team, create_team_membership, or list_team_members, but does not explicitly differentiate from them.

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?

No guidance is given on when to use this tool vs alternatives like create_team_membership or list_team_members. It does not mention prerequisites (e.g., user must be a team admin), nor does it instruct on sharing the inviteLink.

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