upload_app_screenshots

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

With no annotations, the description carries the full burden and does so well: it discloses the destructive replace_existing deletion, the create-if-missing behavior, the append default, the 10-item cap, and the async Apple processing with assetDeliveryState. Nothing important about side effects is left to inference.

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 dense sentences that front-load the core action, then side-effect behavior, then return/async status. Every clause earns its place with no filler.

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 mutation tool with no annotations and no output schema, the description covers purpose, side effects, limits, return value, and the follow-up call needed due to async processing. An agent has everything required to invoke it correctly.

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 the baseline is 3, but the description adds meaning beyond the schema by spelling out the destructive semantics of replace_existing, the in-order interpretation of file_paths, and the 10-screenshot set limit. It stops short of 5 only because display_type values and localization_id sourcing are already in 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?

States a specific verb (upload) and resource (local PNG/JPEG files as App Store screenshots) scoped to one display type of a version localization, in order. An agent can distinguish this from list_app_screenshot_sets and list_app_store_version_localizations without opening a 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?

Explains the key decision point (replace_existing deletes first vs. append) and points to list_app_screenshot_sets for the async-status follow-up. It lacks an explicit 'when not to use' or a named alternative for creating/patching screenshots a different way, so it stops short of a full 5.

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