list_beta_groups

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds only the domain noun 'TestFlight beta groups' and says nothing about pagination, result ordering, or what an empty response means — despite a `next` cursor parameter implying paginated results.

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 front-loaded sentence with zero filler or redundancy. Its brevity is efficient, though it borders on under-specification rather than tightness.

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?

This is a paginated list tool with three parameters, no output schema, and no parameter descriptions, yet the description does not explain pagination, the shape of returned groups, or how to iterate. For a tool whose return contract is entirely undocumented, one sentence is not enough.

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 an app' does imply that appId identifies the parent app and is required, which is useful. However, it says nothing about `limit` or the `next` pagination cursor, leaving two of three parameters entirely unexplained in both schema and description.

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 (list) and resource (TestFlight beta groups) scoped to an app, which cleanly separates it from sibling mutations such as create_beta_group or add_build_to_beta_group. It is clear but does not mention any scope qualifiers or how it differs from list_beta_testers, the nearest read sibling.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., needing an appId from list_apps), and no reference to alternatives. The agent must infer from the name alone that this is the read path paired with create_beta_group.

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