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

Annotations cover the safety profile (not read-only, open-world, non-idempotent, non-destructive), and the description adds substantial behavioral detail on top: a 25-recipient cap, re-send semantics for already-invited people instead of creating duplicates, and the 30-day account-free interview link vs. the normal sign-in invitation.

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 organized so each sentence adds a distinct rule (invitee sourcing, cap, re-send behavior, link expiry, revocation). It is one dense paragraph, but nearly every clause earns its place; only slight compaction would improve it.

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?

With no output schema, the description still conveys the observable outcome (invitation created and emailed, link type depends on team settings, duplicate handling), which is what an agent needs to call it correctly and predict effects.

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 beyond the schema: the source of invitees (org-chart/landscape people tools), the interaction between invitees and includeProcessPeople in the 25-recipient cap, and revocation. It stops short of explaining the message field beyond what the schema already documents.

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: inviting people to record an interview for a named Clarity process and emailing each invitee. It is clearly distinguishable from sibling invite tools (createTeamInvite, bulkCreateTeamInvites, inviteClarityMeetingNotetaker) because it is scoped to Clarity interview invitations.

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?

Explicitly tells the agent to first use the Clarity hierarchy people tools to resolve names/emails, describes when to set includeProcessPeople to true, and names deleteTeamInvite as the way to revoke a pending invitation. When-to-use and the alternative are both stated.

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