upload_ios

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

No annotations are provided, so the description carries the full burden. It usefully discloses that the tool returns before Apple finishes processing, which is a meaningful behavioral trait for a mutation tool, but it omits authentication requirements, whether an existing build is replaced, and what happens to the uploaded artifact.

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 efficient sentence with the core action front-loaded. It is appropriately sized for a one-parameter tool, though the phrase about Apple's processing could be clearer.

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, but the description still lacks essential context for a mutation tool with no annotations: permissions, processing behavior details, and relationship to sibling tools like release_ios. Given the 0% parameter coverage, this leaves too much undocumented.

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 required parameter ipa_path has 0% schema description coverage. The description does not clarify whether the path is local, absolute, remote, or what format is expected, so it does not compensate for the documentation 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 and resource: upload an .ipa to TestFlight. This is clearer than a generic 'upload' and implicitly distinguishes from upload_android, though it doesn't explicitly distinguish from release_ios or status_ios.

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?

No guidance on when to use this versus release_ios, status_ios, or other siblings. The phrase 'without waiting for Apple's processing' hints at an async workflow but doesn't state prerequisites or when-not-to-use conditions.

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