Import App Store context

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose that the data is 'public' and 'current', which suggests no authentication and a fresh read. However, it does not explicitly state whether the operation is read-only, whether it mutates any local/context state, or what happens on an invalid URL or ID.

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 filler. It front-loads the resource and result ('public App Store metadata and current screenshots') before stating the input ('from an App Store URL or Apple ID'), making it easy for an agent to parse quickly.

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 simple one-parameter tool with no output schema, the description identifies the input and the expected result (metadata and screenshots). It is mostly complete, though it does not explain what 'context' means operationally or how the loaded data is returned or stored, which would be helpful.

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 fully describes the single parameter as 'App Store URL or numeric Apple ID' with 100% coverage. The description only restates this same source condition and does not add examples, format details, or constraints beyond what the schema provides.

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 uses a specific verb ('Load') with a specific resource ('public App Store metadata and current screenshots') and an explicit source ('an App Store URL or Apple ID'). It clearly states the tool's function and distinguishes it from search/screenshot-only siblings by covering both metadata and screenshots from a direct identifier.

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 the tool should be used when the agent has an App Store URL or Apple ID, but it gives no guidance on when to choose this over alternatives such as get_app or search_screenshots. It provides no exclusions, prerequisites, or context for selecting the right sibling.

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