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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial semantic behavior: the lab assessment is the only recomputing rubric-backed review, lab_runs are self-reported, other raters are 'never blended', earlier-version reviews are labelled and 'never counted', and comments live in data.reviews[].thread. That is meaningful context beyond the safety profile, though it omits rate/limit behavior.

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?

The purpose is front-loaded in the opening clause and no clause is pure filler — each adds a payload fact. It is, however, one very dense run-on sentence stitched with semicolons, which hurts scannability even if it avoids waste.

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?

Given an output schema exists, the description need not explain return values, yet it goes further and disambiguates the data model (what counts, what is blended, where threads live), which is exactly the hard part for this tool. Combined with annotations covering safety, the only gap is the absence of selection guidance relative to siblings.

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 67%; the subject description is essentially duplicated from the schema ('its id or TYPE:KEY'), while cursor is undocumented in the schema and only lightly covered by 'Page with next_cursor'. The description adds pagination framing but no format or ordering semantics for the cursor beyond the schema.

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 first clause states a specific verb+resource ('Read a subject's reviews') and enumerates the payload categories (owners, lab assessment, lab_runs, other raters, community reviews), so the agent knows exactly what it retrieves. It does not, however, name or distinguish itself from the many adjacent read siblings (read_offering, read_agent, read_work), leaving that inference to the caller.

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 guidance and no when-not or named alternative (e.g., when to prefer resolve_subject or search_subjects). The closest thing to guidance is 'Page with next_cursor', which is invocation mechanics rather than selection advice.

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