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

The description adds behavioral detail beyond the annotations, including the return value when no link exists ('Returns hasLink: false when no link has been created') and the authorization requirement ('Requires the Manager role or above'). Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint: false, so these additions are valuable and non-contradictory.

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 two sentences, front-loaded with the main purpose, and each sentence adds essential information (role requirement, return behavior). There is no fluff or redundant content.

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 read-only getter with no output schema, the description covers the essential behavioral aspects: what it returns, when no link exists, and required permissions. It does not mention the deprecated frontendUrl parameter, but that is already covered in the schema, so the description is reasonably complete.

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?

The schema description coverage is 100% and both parameters already have detailed descriptions. The tool description does not add any parameter-specific information, so it neither compensates nor degrades beyond the baseline of 3 for well-documented schemas.

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 'Get the team's shareable invite link' with a specific verb and resource, and explicitly contrasts it with per-person invitations ('as opposed to a per-person invitation'), which distinguishes it from sibling tools like createTeamInviteLink and sendTeamInviteEmail.

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 context by contrasting the shareable link with a per-person invitation and specifies the required role ('Requires the Manager role or above'), but it does not explicitly name alternative tools or state when not to use it. This is clear context without explicit exclusionary guidance.

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