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

Annotations cover the safety profile (readOnly=false, idempotent=true, destructive=false), and the description adds the auth requirement, the role-restriction behavior, that project access is deferred to rules/grants, and that a single-use link is returned and must be kept secret. That is substantial context beyond the annotations, with no contradictions.

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?

Front-loaded with the core action and scoped well, but it is one dense paragraph and some phrasing ('with the person you act for as the inviter') is heavy. Still, nearly every clause carries information an agent needs.

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 2-param mutation with no output schema but full annotation coverage, the description supplies purpose, auth, role constraints, alternative routing, and the notable return value (single-use link). Nothing essential to calling it correctly 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?

Schema coverage is 100% so the baseline is 3, but the description adds real meaning: the valid role values (Admin, Member, Billing) and the critical exclusion that Owner is refused. That goes beyond the terse schema descriptions.

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 and resource ('Invites an email address into the organization at a platform role') and pins scope to a platform role rather than project-level access. This clearly separates it from siblings like list_members, resend_invitation, and set_member_role.

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 the UI analogue (Settings › Members › Invite member), the prerequisite ('needs Owner or Admin'), and explicitly routes the ownership case elsewhere ('ownership moves by set_member_role once they have joined'). Both when-to-use and the relevant alternative are spelled out.

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