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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds the concrete consequence: the prior URL stops working, so existing holders lose the ability to join. It also discloses a non-obvious authorization requirement (Manager role or above). This is meaningful added context beyond the structured fields.

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?

Three short sentences, front-loaded with the action and scoped artifact, then the destructive consequence, then the permission requirement. No filler.

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 destructive, non-idempotent mutation with no output schema, the description covers the critical risks (irreversible link invalidation, required role) and the schema covers both parameters. It never indicates what is returned (presumably the new link URL), which is the one remaining gap given there is no output schema.

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% — team_id's multi-team/OAuth behavior and frontendUrl's deprecation are fully documented in the schema. The description adds nothing about parameters, so the baseline 3 applies.

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+resource ('Create or regenerate the team's shareable invite link') and disambiguates the artifact as 'the one URL anyone can use to join the team,' which implicitly separates it from the email-based invite siblings (createTeamInvite, bulkCreateTeamInvites, sendTeamInviteEmail). It never names an alternative explicitly, so it falls just short of a 5.

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?

Gives clear context for calling it and a strong caution about the regenerate path ('Regenerating invalidates the previous link'). It also states the role prerequisite (Manager or above). It stops short of naming when to prefer createTeamInvite or bulkCreateTeamInvites instead.

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