List TestFlight testers

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; "Read-only." largely restates that. The description does add value beyond annotations by enumerating the returned fields (name, email, status values, invite source), which matters because there is no output schema.

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?

A single dense sentence with the read-only nature front-loaded and no padding. The leading "Read-only." duplicates the annotation slightly, but the rest of the sentence is tight and information-dense.

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 four-parameter filtered list tool with a fully documented schema and no output schema, the description covers scope, the group-narrowing option, and the shape of the results including status values. An agent has everything needed to call it and interpret the response.

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 description coverage is 100%, so every parameter including the group filter, limit and cursor is already documented in the schema. The description only adds the relational nuance that group scopes within an app, which is a modest supplement rather than new semantics.

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 ("Lists TestFlight testers") and scopes it to an app or one of its beta groups, so it is distinguishable from list_beta_groups. It stops short of naming sibling tools explicitly, which keeps it out of the top band.

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?

Usage is implied: call it when you need the testers of an app or a specific beta group. There is no explicit when-not guidance and no named alternative for related queries (e.g., listing the groups themselves via list_beta_groups).

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