List App Store Charts

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

The description discloses a significant operational cost: 'Full detail makes one additional request per app,' which is beyond the readOnlyHint annotation. It doesn't contradict annotations. It could have mentioned pagination or default behavior, but the per-app request warning adds useful 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 short, front-loaded sentences with no filler. Each sentence adds essential information: the core purpose and the cost caveat.

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 covers the tool's core purpose, category filtering, and a cost caveat. With a fully-described schema and an output schema present, it is sufficient, though it could briefly mention how to select different collections or defaults.

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?

With 100% schema coverage, the baseline is 3. The description adds meaning for 'category' (optional narrowing) and 'fullDetail' (extra request per app), going slightly beyond the schema's descriptions.

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 identifies the tool as retrieving a ranked App Store collection, with optional category narrowing. This distinguishes it from siblings like app_store_reviews, app_store_search, and app_store_developer, which target different resources.

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 use for chart/collection retrieval and notes optional category narrowing, but does not explicitly compare with alternative tools like app_store_search or app_store_app, nor provide when-not-to-use guidance.

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