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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is domain behavior: settings is null until the responder is switched on, auto mode only affects reviews written after enabling and within the star range, and credit usage is included-allowance-plus-1-per-extra-draft. That is meaningful operational context beyond the annotations.

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-loads the resource and its contents, then closes with the null-state caveat and prerequisites. Dense but every clause carries information; the parenthetical about auto-mode scoping and credit pricing is load-bearing rather than filler.

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 usefully enumerates the return payload field-by-field, which is exactly what an agent needs to consume the result. Combined with prerequisites and the null-state rule, it covers the important edges for a single-parameter read tool.

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 the single app_id parameter is already documented as a Sonar UUID that is not a store id. The description reinforces the same constraint ('one of your own iOS apps') but adds no syntax or format detail beyond the schema, so the baseline of 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?

Names a specific resource (the review responder configuration) and enumerates exactly what the returned payload contains: on/off state, manual vs auto mode, instructions, sign-off, language, sync, App Store Connect status, and AI-draft usage. An agent knows precisely what it will receive. It does not explicitly contrast itself with the write sibling sonar_set_review_responder, though the 'settings' framing makes the read intent clear.

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?

Usage is implied rather than stated: this is clearly the read surface to pair with sonar_set_review_responder, but the description never says 'use this before/after setting' or names an alternative. It does supply real prerequisites (Indie plan, App Store Connect connected, own iOS app), which partly compensates.

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