beta_tester_invitations__create

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

Annotations already signal a non-read-only, non-idempotent, non-destructive operation. The description adds that it sends an email and uses POST, but does not disclose consequences like duplicate invitations or whether the tester must already exist. This adds moderate value beyond annotations.

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 HTTP endpoint. It is front-loaded with the action verb and contains no extraneous information.

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?

The description covers the core action and precondition, and the schema handles the request structure. However, it omits context about the 're-send' semantics (that a new invitation record may be created), potential duplicate emails, and the deprecated betaTester relationship. Adequate but not comprehensive for a mutation tool with a complex nested 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 100% because the body parameter has a description, so the baseline is 3. The tool description adds no parameter-level meaning and does not address the deprecated betaTester relationship, but with full schema coverage this is acceptable.

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 uses a specific verb 'Re-send' with a clear resource ('TestFlight invitation email') and a condition ('to a tester who has not accepted yet'), followed by the exact HTTP endpoint. This clearly distinguishes it from sibling create tools like beta_testers__create and beta_groups__create.

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 phrase 'to a tester who has not accepted yet' provides a clear contextual cue for when to use this tool. It does not explicitly name alternatives or exclusions, but the narrow purpose and condition make the usage context obvious.

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