list_beta_groups

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List' implies a read operation, but the description does not mention any behavior such as pagination, sorting, or what happens when no groups exist. It also does not clarify whether both internal and external groups are always returned or if there are any constraints on the app_id.

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 sentence with no filler or repetition, making it efficient and front-loaded. However, it is under-specified, which lowers the score slightly from 5 because conciseness is appropriate but at the expense of necessary details.

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, output schema exists), the description is reasonably complete for the core action, but it lacks context on prerequisites, edge cases, or any additional behavior beyond a basic listing. An agent might still call it correctly, but the missing usage guidance and parameter details reduce completeness.

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 0%, so the description must compensate for the undocumented app_id parameter. It only says 'for an app,' which is vague and does not explain the format, source, or how to obtain a valid app_id. No additional meaning is added beyond the parameter name itself.

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 action ('List') and the resource ('TestFlight beta groups'), with an explicit qualifier ('internal/external') and scope ('for an app'). It distinguishes this from siblings like list_beta_testers (testers vs groups) and list_builds (builds vs groups) without needing to open schemas.

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 implies usage (you need an app_id to list its groups) but does not provide explicit guidance on when to choose this tool over alternatives like list_beta_testers or list_builds. There is no mention of exclusions or alternative tools, so an agent must infer the appropriate context.

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