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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: it defines the meaning of each resulting state (Submitted returns the frozen selection, Pending awaits approval, superseded requires the latest review, expired proves no first commit) and gives retry/polling semantics, which the annotations do not convey.

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 and the non-approval constraint, then organized into state meanings, a when-to-use line, and an example. It is dense and largely earns its space, though the phrasing across state meanings is terse enough to border on cryptic and the example sentence is marginal.

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 shapes need not be explained, and the description nonetheless pre-explains the meaning of each status value plus retry guidance and a fallback when execution is uncertain. For a single-parameter read tool with full annotation coverage, nothing essential 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 there is a single parameter whose 'unchanged receipt' semantics are already documented in the schema. The description reinforces that the receipt must be unchanged and ties it back to review_proposed_updates, but adds no syntax or format detail beyond the schema, so the 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 and resource ('Read a review's shared status') and immediately scopes it against siblings by saying 'without approving or executing changes', which contrasts with commit_reviewed_updates and review_proposed_updates. An agent can distinguish it from the other review tools without opening a schema.

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 'When to use' line gives an explicit trigger ('Synchronize a review after chat approval or correction, using its unchanged receipt'), and it adds a concrete alternative behavior ('inspect CRM state before another save') plus polling discipline ('Poll with backoff only while viewing a pending or executing review'). It stops short of naming the specific sibling tool to use instead for the fallback inspection, so it is clear but not fully routing.

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