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

Annotations already declare readOnlyHint/destructiveHint/openWorldHint, so the safety profile is covered. The description still adds real value beyond them: it discloses the scope ('submissions created outside nomac') and an important limitation ('Apple does not expose reviewer correspondence through its public API'), which the agent could not learn from annotations or schema alone.

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?

Three sentences, front-loaded with the core read action and scoping, with no filler. Slightly dense but every sentence carries distinct information (scope, parameter effect, API limitation).

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?

An output schema exists, so return values need not be described, and the description covers scope, the optional parameter's effect, and a known data limitation. The main missing piece is routing guidance against the review/testflight siblings, which keeps it short of a 5.

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 is 3, but the description adds meaning the schema lacks: it explains that asc_submission_id unlocks version/build/contact/attachment details, whereas the schema only labels it as an ID sourced 'from get_review'. This makes it clear why and when to pass the optional parameter.

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 live App Review submissions and all item states') and even extends scope to submissions created outside nomac. It does not, however, name or distinguish itself from close siblings like get_testflight, update_review, or prepare_review_reply, so the agent must infer the boundary.

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 line 'Pass asc_submission_id for version/build/contact/attachment details' implies when to supply the optional parameter, and 'read live' implies a status-check use case. But there is no explicit when-to-use/when-not guidance and no named alternative among the review-related siblings, so usage is only implied.

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