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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context: pagination semantics (10 per page, hasMore/memberHasMore), that counts are unfiltered, corrections replace answers, undo removes them, and that list membership is never approval. No contradictions with 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?

The description is efficient and front-loaded, starting with the core purpose and then adding necessary behavioral details. Each sentence adds value—pagination, counts, and the approval caveat—without redundancy. It is slightly long but appropriately so for the complexity.

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 that an output schema exists, the description need not detail return values, but it still mentions key returned fields (setupState, reviewerUserId, reviewScope, review_url). It covers pagination and the dual-listing behavior (answers vs eligible memberPersonIds) thoroughly. Minor gaps remain around parameter usage (e.g., list_id vs list_name), but overall it is fairly complete for a read tool with this complexity.

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%, so the description carries the full burden for parameter meaning. It mentions 'page' in the context of pagination and implies 'answer' as a filter, but does not explain the roles of list_id vs list_name, nor the exact filtering behavior of the 'answer' parameter. Given the 0% coverage, the description does not sufficiently compensate.

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 description clearly states the tool reads the authenticated user's latest review answers and counts, using a specific verb (Read) and resource (list reviews). It distinguishes itself from sibling tools like configure_list_review by emphasizing 'read only' and 'reviewScope=self', making it unambiguous which tool to use for reading own reviews.

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 description provides context on how to use the tool (pagination, verifying batches) but does not explicitly contrast it with alternatives like configure_list_review or list_lists. It implies when to use it (to read reviews) but lacks explicit 'use this instead of X' guidance, leaving some inference to the agent.

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