upload_binary

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

No annotations are provided, so the description carries the burden of disclosing behavior. It states the upload is a write operation requiring 'confirm:true' and mentions the 'Pro feature' gating, which is useful. However, it doesn't disclose what happens with 'confirm:false,' the return format, or any side effects (e.g., does it replace an existing build?). Still, the presence of explicit confirmation is a meaningful behavioral disclosure.

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 compact: one sentence plus two short contextual flags. It is front-loaded with the core action and includes high-value notes (confirm requirement, Pro feature) without rambling. Slight deduction for not using structured formatting (e.g., bullets) but it's 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?

Given this is a write/intructive tool with no annotations and no output schema, the description covers the essentials: what is uploaded, how, and the confirmation requirement. However, it omits details like whether the tool waits for Apple's processing, returns a tracking ID, or what errors to expect if the API key is invalid. For a Pro-feature upload tool, more detail would be helpful, but it is minimally viable.

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%, so the schema already documents all parameters. The description adds minimal extra meaning beyond the schema, except that 'confirm' is mandatory for the upload to actually happen, which is also partially in the schema ('Must be true to actually upload'). The description does not clarify things like absolute path format or platform defaults beyond the schema.

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 a specific action: 'Upload a signed .ipa to App Store Connect via altool, using your API key.' This distinguishes it from siblings like 'upload_screenshots' and 'attach_build,' though it doesn't explicitly name an alternative tool. It identifies the resource (.ipa), the destination (App Store Connect), and the mechanism (altool/API key).

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?

It gives clear context on when to use it (uploading a signed .ipa to App Store Connect) and the mechanism (via altool with API key). It also notes the confirmation requirement ('requires confirm:true') and that it is a Pro feature. While it doesn't explicitly contrast with sibling tools like 'upload_screenshots' or 'attach_build,' the resource specificity makes the use case clear.

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