remove_testers_from_beta_group

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing about what removal does (irreversibility, effect on installed builds, per-tester failure handling) and instead contributes an irrelevant statement about adding sending invitations.

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 first sentence is tight and front-loaded, but the second sentence about adding invitations does not earn its place in a removal tool and adds ambiguity.

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?

With no output schema and 0% parameter documentation, the description should explain the effect of the destructive removal and the parameters. Instead it leaves both undocumented and includes a mismatched sentence, so it is not complete enough for a destructive batch operation.

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 carry the parameter meaning, yet it explains neither betaGroupId nor betaTesterIds (an array of at least one tester ID). The agent gets no added semantics beyond the property names.

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 first sentence names a specific verb and resource ('Remove existing TestFlight testers from a group'), which clearly separates it from the sibling add_testers_to_beta_group. There is no explicit sibling callout, but the add/remove contrast is implied.

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 statement of when to use this versus add_testers_to_beta_group or other tester tools, and no prerequisites such as needing an existing beta group. The only contextual sentence discusses 'adding', which gives no guidance on removal usage.

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