App Store live-preview payload (internal)

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

Annotations already declare readOnlyHint=true. The description adds that 'nothing is installed' and describes the sandboxed nature with 'mock-data fixtures' and 'LIVE sandboxed preview card,' which goes beyond the annotation. No contradiction.

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, front-loaded with 'Internal,' and each sentence conveys a distinct piece of information: what it returns, why it exists, and that it's safe and not for direct use.

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 tool has a single parameter, an output schema, and annotations. The description covers the purpose, internal nature, side-effect-free behavior, and sandboxed output. Nothing critical is missing.

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 only parameter 'name' is documented in the schema with reference to app_store_list, so coverage is 100%. The description itself doesn't add any parameter detail, so baseline 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 uses 'returns' as the verb and specifies the resource: an App Store entry's ui, manifest, and mock-data fixtures. The 'Internal' prefix and 'Not useful to call directly' clearly distinguish it from sibling tools like install_from_app_store or get_app. It's specific about the purpose: rendering a sandboxed preview card.

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?

Explicitly marked 'Internal' and 'Not useful to call directly,' which tells agents not to invoke it directly. However, it does not name an alternative tool to use instead, so it earns a 4 rather than 5.

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