Browse Store Chart

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

With no annotations, the description carries the behavioral disclosure burden. 'Browse' implies a non-mutating read, but the description does not explicitly state side-effect-free behavior, result shape, or any constraints such as pagination or locale behavior.

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?

A single sentence that front-loads the resource and enumerates the three chart types. There is no filler or redundant explanation.

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 that all six parameters are optional and fully described in the schema, and an output schema exists, the description does not need to explain return values. It is sufficient for a simple read-only chart lookup, though it could have added explicit read-only confirmation and alternative tool routing.

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 coverage is 100%, so the baseline applies. The description adds only a modest semantic link between 'top free/top paid/top grossing' and the collection values TOP_FREE/TOP_PAID/GROSSING; the parameters themselves are already documented in the schema.

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 names a concrete resource ('store chart') and the three collection variants (top free, top paid, top grossing), which maps cleanly to the collection parameter and sets it apart from search or listing tools. It is clear, though the verb 'browse' is generic and no sibling is explicitly referenced.

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 intended use is implied: get ranked store charts. However, there is no explicit statement of when to use it over alternatives or when not to use it, even though many nearby tools (e.g., search_store, get_store_listing) could overlap.

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