add_build_to_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 'MUTATES' framing largely restates what structured data provides. The description does add the useful precondition that the build must be processed, but it says nothing about whether existing group membership is affected, whether re-adding is a no-op, or what authorization is required.

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 the mutation warning first and the effect second; no filler, though the all-caps 'MUTATES' is stylistic rather than informative.

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 non-idempotent destructive mutation with two undocumented required IDs and no output schema, the description omits expected outcomes, error conditions, and how the IDs are sourced. Only the 'processed build' precondition is covered.

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% for both required parameters (buildId, groupId) and the description supplies no meaning for either. It doesn't clarify identifier format or where to obtain the IDs, so it fails to compensate for the coverage 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 ('assign') and resource ('a processed build to a beta group') scoped to TestFlight access, so an agent can tell it apart from add_tester_to_beta_group or create_beta_group without opening the schema.

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 explicit when-to-use or when-not-to-use guidance, no mention of alternatives such as assign_build_to_version, and no statement of prerequisites beyond the parenthetical 'processed build'. The agent is left to infer context.

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