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

Beyond the annotations, the description discloses the full lifecycle: nothing is sent and no seat is consumed until the owner confirms on the website, the owner is normally emailed, and repeat calls return the open request (reinforcing idempotentHint). It also adds authorization and plan constraints that the annotations do not convey.

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 front-loaded with the core action and the confirmation requirement, and each sentence carries useful information. The line about the owner seeing the request on the website slightly repeats the earlier confirmation sentence, costing a bit of tightness.

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 single-parameter tool with an output schema and rich annotations, the description covers what an agent needs: preconditions, side effects, deferred confirmation, and duplicate behavior. Nothing material is 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?

There is only one parameter and schema coverage is 100%, with the schema itself saying "The address to invite." The description refers to "someone" and "the same address" but adds no format or constraint detail beyond the schema, 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?

"Ask to invite someone to the team" names a specific verb and resource, and the follow-up sentence clarifies that this creates a pending request rather than sending an invitation. That nuance separates it from resend_team_invitation, though no sibling is named outright.

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?

It states the preconditions for use clearly: the caller must be the account owner's API key or connected app and the plan must include team seats. "Asking again for the same address returns the open request" implicitly tells the agent not to re-invoke for duplicates, but alternatives like resend_team_invitation are not explicitly referenced.

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