beta_groups__beta_testers__add

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

Annotations indicate a mutation (readOnlyHint=false) and not destructive or idempotent. The description adds that testers must be 'existing,' which implies a precondition. However, it does not explain side effects, such as whether duplicate additions are ignored or cause errors, leaving behavioral details incomplete.

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 description is a single concise sentence plus the endpoint reference, with no redundant or unnecessary content. It is front-loaded and efficient.

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 simple add operation with no output schema, the description is adequate but lacks details on response format, error handling, or relationship to sibling tools. It is minimal but not misleading.

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 coverage is 100% with both parameters described in the schema. The description neither adds nor contradicts the schema; it merely lists the parameters implicitly through the endpoint path. Baseline score of 3 is appropriate.

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 description clearly states the action (Add), the target (existing beta testers to a TestFlight group), and includes the endpoint for reference. It is specific and distinguishes from siblings like beta_groups__beta_testers__remove and beta_testers__beta_groups__add, though it does not explicitly differentiate direction.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites (e.g., testers must already exist), and no context on idempotency or error conditions. It is purely a statement of action.

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