add_testers_to_beta_group

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

The note that 'Adding may send invitations' adds genuine value beyond the annotations, explaining the open-world side effect consistent with openWorldHint=true and destructiveHint=true. However, it does not say how duplicates are handled (idempotentHint=false suggests repeat adds may fail or duplicate) or that removal requires a different tool.

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?

Two short sentences, front-loaded with the action and followed by the side-effect warning. No filler.

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 a two-param mutation whose annotations already declare destructive and non-idempotent behavior, the description covers the essential side effect but leaves duplicate-handling and result expectations unexplained. Adequate, not complete.

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% and neither betaGroupId nor betaTesterIds has any schema documentation. The description conveys only that the IDs refer to an existing group and existing testers; it gives no detail on batch limits, ID format, or what happens when a tester is already in the group.

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 and resource ('Add existing TestFlight testers to a group'), and the word 'existing' plus 'testers' differentiates it from add_build_to_beta_group and create_beta_tester. It does not explicitly name those siblings, but the resource added is 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?

'Add existing TestFlight testers' implies testers must already exist (create_beta_tester) and that the group must exist first, but this is inference rather than stated guidance. No explicit when-to-use vs. add_build_to_beta_group or remove_testers_from_beta_group.

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