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

readOnlyHint already covers safety, and the description still adds substantial behavioral context: the exact returned fields, the conditional presence of email keyed to hasAccount, and the reason (tester email addresses are not exposed over this connection). The id-to-invitationId cross-reference with the funnel tools is non-obvious operational knowledge found nowhere in the annotations.

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-loads what the tool lists, then the return shape, then the email caveat, then the routing guidance. The email/hasAccount sentence is long and slightly dense, but every clause carries real information for handling rows, so nothing is wasted.

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?

There is no output schema, so the description carries the return-shape burden and does so precisely (id, name, invitedAt, lastPingAt, hasAccount, conditional email). For a single-parameter read tool, an agent needs nothing further to call and interpret it.

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?

Only one parameter and schema coverage is 100%, so the schema already fully documents productId, including how to obtain valid IDs. The description reinforces that the query is scoped to a beta project but adds no format or constraint detail beyond the schema, making 3 the correct baseline.

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 (list pending, not-yet-accepted tester invitations) scoped to the beta project, and explicitly separates itself from getBetaTesters. An agent can distinguish it from listOrganizationTesters or inviteTesters without opening a schema.

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 an explicit use case (identify testers who haven't joined and may need a reminder), names the follow-on tools for acting on results (pingTesters, cancelInvitations), and states the exclusion that these invitees do not appear in getBetaTesters. When-to-use and when-not-to-use are both covered.

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