List Screenshot Sets

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, so the safety profile is well-covered. The description adds little beyond 'list', but does not contradict annotations. It could mention pagination behavior, but the schema already documents limit and nextUrl.

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 sentence with no unnecessary words. It is appropriately sized for a straightforward list operation and front-loads the core action.

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?

While the tool is simple and annotations cover safety, the description lacks details about the output (no output schema) and fails to explain the required localizationId parameter. For a list tool, agents would benefit from knowing what fields are returned. Still, it is minimally adequate given schema coverage of limit and nextUrl.

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 67% (limit and nextUrl documented), but the required parameter localizationId has no description in schema or in the tool description. The description does not compensate by explaining what localizationId refers to (e.g., from asc_list_version_localizations). This is a significant gap for a required parameter.

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 action (list) and the resource (screenshot sets) within a specific context (App Store version localization). This distinguishes it from sibling tools like asc_list_screenshots (individual screenshots) and asc_create_screenshot_set (create).

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 implies that a localizationId is needed, but provides no explicit guidance on when to use this tool versus alternatives (e.g., asc_list_screenshots) or when not to use it. The context is clear from the purpose, but no exclusions or prerequisites are stated.

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