List App Store analytics reports

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavioral context beyond that: the setup dependency and the dual-mode behavior (listing reports vs. listing dates for one report). It does not describe pagination, auth, or output shape.

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 efficiently structured sentence front-loads the primary action and uses a parenthetical to enumerate categories without waste. The precondition sentence is short and earns its place.

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, the description covers purpose, modes, and the setup prerequisite. Return-value details and pagination behavior are unstated, but the core information needed to invoke it correctly is present.

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 only 33%, with reportId being the sole documented parameter. The description partially compensates by enumerating the category families and explaining the reportId mode, but appId's format/role and the category's default behavior are left implicit.

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 states a specific verb (List) and resource (analytics reports for an app), enumerates the report families, and explains the second mode triggered by reportId. This clearly distinguishes it from download-oriented siblings such as asc_download_analytics_report.

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?

It gives a concrete precondition — reports only exist after asc_analytics_setup has run — and explains the reportId branch for retrieving available dates. It does not explicitly name alternative tools or state when not to use it, keeping it below a 5.

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