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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered; the description adds the non-obvious behavioral caveat that panel respondents are not returned by this tool, which prevents a confusing empty/error result. It also flags that a personal interview link and reward state are exposed, which is useful sensitivity context.

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 sentences, front-loaded with what is read and what is returned, then the usage rule and the exclusion. No filler, and the most decision-relevant constraint (panel respondents excluded) is one short clause.

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 an output schema available the description needn't enumerate return structure, and annotations cover the safety profile; the description still supplies the use-case and the respondent-type exclusion. The only thin spot is that multi-organization context is left entirely to the schema field text.

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 50%: organization_id is described in the schema (billing scope, use list_organizations), while participant_id carries only format/pattern constraints. The description adds no syntax or selection guidance for either parameter, so the schema does most of the work and the description only implies that a single participant is addressed.

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 ("Read one BYOP invitation") plus the exact fields returned (status, interview link, interview count, reward state), which is far more informative than the bare name. It also draws the boundary with panel respondents, so an agent can tell this apart from list_participants and other read tools.

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?

"Use it to verify the participant before changing their email, deleting the invitation, or sending a reward" gives concrete trigger conditions that map onto the sibling mutations update_participant, delete_participant, and send_participant_reward. It stops short of naming those siblings explicitly or saying when not to call it (e.g., how to discover the ID in the first place).

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