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

No annotations are provided, so the description must carry the behavioral transparency burden. It does disclose the return value ('Returns the list of created invitation summaries') and the prerequisite workflow, plus a token cost. However, it omits key behavioral traits such as whether emails are sent, whether invitations expire, or any permission requirements. It implies a mutation but doesn't fully describe side effects.

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 four sentences, each earning its place: purpose, prerequisite, return type, and cost. It is front-loaded with the core action and avoids redundancy with the schema. There is no fluff or filler.

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?

Given the schema fully describes parameters and an output schema exists, the description covers the essential context: what the tool does, what to call first, what is returned, and cost. It lacks caveats about invitation behavior (e.g., email delivery, expiration) but is generally complete for an agent to use the tool correctly.

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 already has 100% parameter description coverage, so the baseline is 3. The description adds value beyond the schema by explaining the workflow for clerk_instance_id: 'Pass clerk_instance_id to target a specific connection, or omit it to use the default account,' and explicitly instructs to call clerk.get_connected_accounts first. This clarifies the optional parameter's role in multi-account contexts.

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 a specific action: 'Invite one or more email addresses to join a Clerk organization with specific roles.' It names the resource (organization) and distinguishes this from sibling tools like clerk.create_invitations (general invitations) and clerk.create_organization_membership (adding existing users). The verb 'invite' and the scope 'organization' make the purpose unambiguous.

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 clear context: it is for inviting email addresses to join an organization. It also gives a prerequisite instruction: 'Call clerk.get_connected_accounts first' and explains how to use clerk_instance_id. However, it does not explicitly name alternatives or state when not to use this tool, such as comparing to clerk.create_organization_membership for existing users.

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