Top charts

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network reach are covered. The description adds that category filtering is optional, but says nothing about result ordering, pagination limits, or the difference between the two similarly named output-shaping flags (verbose vs fullDetail), which is exactly the kind of behavioral detail annotations cannot carry.

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?

One sentence, front-loaded with the action and resource, with the optional filter trailing. No filler. It is arguably too terse for a 7-parameter tool, but nothing in it is wasted.

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 is simple and the schema is fully self-documenting, so most of the burden is met elsewhere. However, with no output schema and two overlapping flags (verbose and fullDetail) whose interaction is unexplained, an agent must guess what it will actually receive back.

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 description coverage is 100%, so every one of the 7 parameters is already documented, including defaults, enum values, and the 200 max. The description only restates the chart examples that the collection enum already lists, adding no new meaning; 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?

States a specific verb and resource ("Get apps from an App Store chart/collection") and enumerates example charts (top free, top paid, top grossing, new), so the agent knows this is a chart-browsing tool rather than a keyword search. It never names the sibling search_apps, so the distinction from search-style tools is left implicit.

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 phrase "chart/collection" plus the optional category filter implies browsing-oriented usage, but the description never says when to prefer this over search_apps, similar_apps, or developer_apps. No exclusions, no prerequisites, no mention of default behavior when no collection is supplied.

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