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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds one genuine behavioral note (resend queues Mailer delivery, i.e. async), but does not disclose whether revoke is irreversible, what permissions are required, or that get_link is a read operation inside an otherwise destructive tool.

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?

Two compact sentences with the operation set front-loaded and zero filler. No restatement of the title and no redundant prose.

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 moderate-complexity mutation tool with no output schema, the description identifies all three modes but omits prerequisites, permission needs, and reversibility of revoke. Annotations cover the destructive/safety profile, so the gaps are survivable but not 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?

Schema description coverage is 0%, so the description must carry the load. It only restates the action enum values (resend/revoke/get_link) and clarifies marginally what resend and get_link do, but says nothing about inviteId or organizationId, leaving two of three parameters undocumented in both schema and 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 states specific verbs and a specific resource: resend, revoke, or get the live acceptance link for a Team invitation. An agent can distinguish this from update_team and update_team_member by the 'invitation' resource. It does not explicitly name the sibling alternatives, keeping it just below 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?

The three action values are enumerated, which implicitly tells the agent this tool has three operating modes, but there is no explicit guidance on when to choose each mode or when to prefer this tool over a sibling like invite_team_member. Usage is left to inference from the self-describing action names.

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