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

Without annotations, the description carries the full behavioral burden. It usefully discloses the two supported image sources, the default display type, and the legacy file-path constraint, but it does not say whether an upload overwrites an existing slot image, what permissions are required, or what errors can occur.

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 and front-loaded with the core action, followed by the per-slide usage rule and the file-path caveat. Every clause adds actionable 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?

For a six-parameter mutation tool with no annotations and no output schema, the description covers the main upload mechanics well but leaves gaps around localization targeting, notification_message behavior, overwrite semantics, and return/error behavior. It is adequate but not fully complete.

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 67%, and the description adds meaningful semantics for the key upload parameters: base64 is marked as MCP-preferred, URL is described as an https master image, and file_path is described as legacy and replay-host-only. It also associates the default APP_IPHONE_65 size with the display type, though localization_id and notification_message remain largely schema-documented.

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 one App Store screenshot into a single carousel slot. The singular, slot-oriented phrasing implicitly distinguishes it from the plural upload_screenshots sibling, though it does not name that sibling explicitly.

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?

Gives clear operational context: call once per slide, default size APP_IPHONE_65 / 6.5″, and the constraint that screenshot_file_path only works on the replay host. It does not explicitly compare against upload_screenshots or state when not to use this tool.

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