upload_ios_screenshots

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

Adds behavioral context beyond annotations: describes format constraints (PNG no alpha, JPEG), size limit (10 MB), count limit (10 per set), and the effect of replace (delete existing before upload). Annotations only provide readOnlyHint and destructiveHint, so description adds significant value.

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?

Four sentences, each serving a purpose: summary, constraints, prerequisite, recommendation. No redundant or filler content. Front-loaded with most important 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?

Given the tool has 6 parameters, no output schema, and moderate complexity, the description covers prerequisites, constraints, and parameter rationale. Could mention that screenshots are linked to the specified app_id and version, but overall adequate for agent understanding.

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 100%, so baseline is 3. Description adds value by explaining device_type requires prior API call and recommends replace=true. Provides practical usage context for parameters beyond schema descriptions.

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 the verb 'upload' with specific resource 'iOS screenshots to App Store Connect for a specific device type and locale.' It distinguishes from sibling tools like upload_android_screenshots by specifying platform and screenshot type.

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?

Provides when-to-use guidance: recommends setting replace=true for refreshing a set. Advises calling list_ios_screenshot_types first for valid device_type values. Does not explicitly mention when not to use, but context of sibling tools implies differentiation.

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