submit_beta_review

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true), so the safety burden is partly carried. The description usefully adds the prerequisite chain and the pre-condition that the build must be "processed," but says nothing about consequences — whether the submission can be withdrawn, what state the build enters, or typical review turnaround — which matters far more given destructiveHint=true.

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 tight sentences — the action and scope first, the disambiguation second. Every clause carries information; no filler or restatement of the title.

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 one-parameter submission tool with no output schema, the essentials (what it does, prerequisites, disambiguation) are covered. Missing are what the caller gets back or should do next — the tool has no output schema and the description does not route to get_beta_review_status — and any clarification of the required buildId format.

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?

The single parameter (buildId) has 0% schema description coverage and the description never mentions it, so the agent gets no guidance on whether this is an App Store Connect build identifier versus a build/version number, nor how to obtain it. The only implicit hint is "processed build," which gestures at a required build state but never links it to the parameter.

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?

Names a specific verb and resource ("Submit a processed build for TestFlight external Beta App Review") and explicitly scopes it against App Store review, which is the sibling operation an agent could easily confuse it with (submit_for_review). An agent can route correctly 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?

States the preconditions (beta app description, review contacts, export compliance must be complete) and rules out the App Store review path via "This is separate from App Store review." It stops short of naming the actual sibling tools to use for those prerequisites (e.g., set_build_export_compliance) or for checking the resulting status (get_beta_review_status).

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