appstore_editorial

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

With no annotations, the description carries full responsibility for behavioral disclosure. It lists valid device enum values, explains the section enum, and warns about the 400 error for watch+arcade. It also references the source content (apps.apple.com device switcher). While it omits output shape or pagination, it covers the most important behavioral traits for this simple retrieval tool.

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 three sentences, each contributing unique value: the first identifies the action, the second gives an external reference, and the third details the enums and edge case. It is front-loaded and contains no filler.

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?

Given no output schema and no annotations, the description captures the tool's core behavior, parameter enums, and an error scenario. It doesn't discuss lang/country defaults, but the schema descriptions for those are adequate. For the tool's complexity, the description is sufficiently complete.

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 input schema provides generic descriptions like 'Apple device catalog' and 'Editorial section within the device.' The description enriches these by enumerating exact values, defining what each section means, and flagging an invalid combination. This is essential guidance for an agent to choose correct 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 begins with a clear action and target: 'Retrieve an App Store device or Arcade editorial landing page.' It specifies the output as curated editorial shelves and differentiates itself from sibling tools like appstore_search or appstore_list by focusing on per-device landing pages.

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?

Provides clear context on when to use: for per-device App Store editorial pages, matching apps.apple.com's device switcher. It details device and section choices but does not explicitly name alternatives or exclusion cases, though the specificity makes the usage obvious.

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