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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond that: the Manager-or-above role requirement and the fact that the response includes hasLink: false when no invite link exists. This is meaningful disclosure for a simple getter with no output schema.

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 compact sentences with no filler. The core purpose is front-loaded, followed by a return-value edge case and an access requirement. Every sentence contributes useful information.

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 tool's essential behavior, the no-link case, and the required role. With no output schema, it does not enumerate the full response shape, but for a simple getter this is adequate and no critical calling context appears missing.

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%, and both team_id and frontendUrl are already thoroughly documented in the schema. The description does not add parameter-level detail, but the schema carries the meaning, so a baseline 3 is appropriate.

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?

Description states a specific verb and resource: get the team's shareable invite link, and differentiates it from a per-person invitation. It clearly distinguishes this read-only retrieval tool from sibling operations like createTeamInviteLink or 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 gives clear context for when to use this tool: when you need the single team-wide invite URL, and explicitly contrasts it with per-person invitations. It does not name specific alternative tools, but the exclusion is clear and the role requirement adds practical usage guidance.

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