Create a beta group

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description adds genuinely new context on top of that: it requires ASC_WRITE=1, mutates App Store Connect, and concretely explains idempotency ('steps already done are skipped'). Return format is unaddressed, but no output schema exists to cover it.

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?

Purpose is front-loaded in the first sentence and the supporting detail is broken into short, scannable blocks with no filler. The trailing paragraph is slightly fragmentary ('Changes App Store Connect (needs ASC_WRITE=1). Safe to re-run...') but each clause earns its place.

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 an eight-parameter mutation tool with no output schema, the description supplies the key operational facts: auth requirement, idempotency, and the semantic difference between the two group types. Only per-parameter behavior for the optional flags is left entirely to the schema.

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 75% and eight parameters exist, so the schema carries most of the load. The description adds conceptual meaning for the external/internal split and the public-link concept, but says nothing about feedback, all_builds, or public_link_limit, so it does not compensate for the remaining gap.

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+resource ('Creates a TestFlight group') and immediately discloses upsert semantics ('or returns the existing one with the same name'), which cleanly separates it from list_beta_groups and invite_testers in the sibling set.

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?

Explains the internal vs external group distinction and what each can contain, giving the agent a clear basis for choosing a mode. It does not name an alternative tool or state when not to use this one, so it stops short of full routing guidance.

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