[Read] List screenshot sets

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

With no annotations, the description carries the full burden and explicitly states 'Read-only,' disclosing the non-mutating behavior. It also explains that sets are organized one per device display type, giving insight into the output structure. It lacks deeper details like pagination or error behavior, but is adequate for a simple read operation.

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 a single, front-loaded sentence that begins with 'Read-only' and states the action and scope concisely. Every word contributes meaningful detail, with no redundancy or extraneous content.

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 straightforward list operation with three well-documented parameters and no output schema, the description provides sufficient context: it states the read-only nature, what is listed, and the required scope (version/locale). It does not enumerate return fields, but that is beyond minimal expectations for this simple tool.

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 schema already covers all three parameters with descriptive text (e.g., appId as 'Bundle id, app name, or App Store Connect app id'). The description adds conceptual context about screenshot sets but does not significantly enhance understanding of the parameters themselves, so the baseline score of 3 applies.

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 tool's function: it lists App Store screenshot sets for a given version/locale, with a specific example (APP_IPHONE_67). This distinguishes it from sibling tools like asc_screenshot_upload or asc_versions_list, which address different resources or actions.

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?

The description provides clear context: use this to read screenshot sets for a specific app version and locale. It does not explicitly mention alternatives or exclusions, but the read-only nature and resource focus imply the appropriate use case.

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