screenshot_mobile

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

No annotations are provided, so the description must carry the full burden. It mentions return content (screenshots, metadata) but does not disclose behavioral traits such as rate limits, authentication requirements, or whether it is read-only. The description gives moderate insight but lacks full transparency.

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?

Two sentences cover the action, parameters, and return information without any fluff. Every sentence serves a purpose, making it highly concise and well-structured.

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?

The description explains return values (screenshots and metadata) adequately for a tool with no output schema. Parameters are well-documented in the schema. It lacks some behavioral context (e.g., waiting behavior) but is otherwise complete for a fetching 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?

Schema description coverage is 100%, so the baseline is 3. The description adds little beyond the schema, only rephrasing that parameters allow search by name or bundle ID. No additional meaning or usage details are provided for individual parameters.

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 it fetches app store listing screenshots for iOS or Android apps by name or bundle/package ID. It distinguishes from sibling tools like screenshot_web (web screenshots) by specifying the resource as app store listings. The verb 'Fetch' and resource are specific and unambiguous.

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 usage for mobile app screenshots but does not explicitly compare to alternatives like screenshot_web or state when not to use this tool. No exclusions or alternative recommendations are provided.

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