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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. Beyond that the description adds real context: data is fetched live from App Store Connect and includes items, and it explains the emptyDraft marker as an artifact of an interrupted submit — an edge case an agent would otherwise misread.

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 dense sentences with the core action and scope front-loaded, then the emptyDraft edge case. The second sentence is a little compressed and jargon-heavy but carries non-obvious information, so it 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?

With no output schema the description does well to say results come back with their items and to explain one returned marker. But it says nothing about the appId the caller must supply, result ordering, or whether all open submissions across versions are returned — enough gaps to be only adequate.

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 0% and the single required parameter appId is never mentioned in the description, so nothing clarifies that it identifies the App Store Connect app whose submissions are listed. The parameter is guessable from the tool title but is not actually documented anywhere.

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 ('Read the App Store review submissions ... live, with their items') and scopes it to submissions still open on App Store Connect. It does not, however, distinguish itself from the sibling list_reviews, leaving the agent to infer that one is customer reviews and the other is submission records.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative; nothing tells the agent whether to reach for this or list_reviews / check_apple_release. The only hint is the implicit 'still open' filter, which is scope rather than routing advice.

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