apple_testflight_invite

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

With no annotations, the description carries the full burden and does well: it flags 'External action', discloses the side effect that a group is created if `group_name` doesn't exist, and states the team-membership prerequisite. It omits auth/permission requirements and reversibility (how to revoke an invite), keeping it short of a 5.

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?

Three sentences, purpose front-loaded, with the prerequisite and group-creation behavior following. No filler, though the parenthetical aside is slightly verbose.

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?

An output schema exists so return values need not be explained. For a side-effecting mutation with no annotations, the description covers the prerequisite, the create-if-missing behavior, and the external-action nature, leaving only permission/reversibility details unstated.

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 0%, so the description must compensate. It clarifies the most non-obvious parameter (`group_name` auto-creates a group with that name) and implies email is the invitee, but app_id, first_name, and last_name are left entirely undocumented.

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 ('Invite') and resource ('internal TestFlight'), and clarifies what an internal group means (a group that receives every build). No sibling tool covers TestFlight invites, so it is cleanly distinguishable.

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?

Gives a clear prerequisite (the invitee must already be a team user in App Store Connect, check Users and Access) and notes that internal testing skips review. It provides context for when this applies but names no explicit alternative tool or exclusion conditions.

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