[Read] List TestFlight beta groups

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states 'Read-only', which signals no side effects, and further describes what the response includes (internal group flag, public link sharing enabled). This is sufficient for a simple list tool, though it doesn't cover error handling or authorization requirements.

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 a single, front-loaded sentence beginning with 'Read-only' followed by the action. It contains no fluff or redundant information; every word contributes to understanding the tool's purpose and output.

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 tool's simplicity (one parameter, no output schema, no annotations), the description is fairly complete. It explains what is returned (groups with internal and public link flags) and that it is read-only. It does not describe pagination or error cases, but for a list operation this is not a critical gap.

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 input schema covers the only parameter (appId) with a clear description of accepted values, so schema coverage is 100%. The description does not add extra meaning to the parameter beyond what the schema already provides. Baseline 3 is appropriate since the schema carries the semantic burden.

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 the tool's purpose: 'Lists TestFlight beta tester groups for an app' with a specific verb and resource. It also distinguishes itself from siblings by noting it lists groups, not adds builds or manages localizations. The inclusion of examples ('Internal Testers') and output details (internal group status, public link sharing) makes 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 a read-only operation for listing beta groups, implying it should be used to retrieve group information rather than modify it. However, it does not explicitly name alternatives or when-not-to-use scenarios, so it falls short of a 5. The 'Read-only' tag gives enough guidance for safe use.

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