Top and new apps

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

Annotations already declare readOnly/idempotent/openWorld, so the bar is low, and the description adds real context beyond them: store-wide 'best' means Bazaar trending or Myket editorial with no ranking guarantee. It doesn't cover auth needs or result-size/pagination behavior, keeping it from a 5.

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?

Front-loaded with the core action, then mode/scope caveats and handoffs in three short sentences; every sentence carries information. The parenthetical-heavy style is dense but not padded.

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?

For a read-only listing tool with no output schema and fully documented parameters, the description covers mode selection, scope constraints, slug sourcing and next-step routing. Nothing an agent needs to invoke it correctly 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?

Schema description coverage is 100% and each parameter already carries enum values, defaults, page sizes and the 'best only' store-wide rule. The description adds cross-store slug variability, but much of its parameter meaning (category required for 'new') restates what the schema already documents, 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?

States a specific verb+resource (list top/newest apps or games) and explicitly distinguishes the two modes ('best' vs 'new') and the two scopes (per-category vs store-wide). It also names the sibling tools it hands off to (ap_categories, ap_app, ap_compare), so an agent can separate it from ap_search without opening schemas.

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?

Gives clear usage conditions: 'new' requires a category, slugs come from ap_categories and differ per store, and follow-up goes to ap_app or ap_compare. It does not state when to prefer this over ap_search or ap_similar, so it stops short of full when-not coverage.

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