review_list

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so 'Read-only' mostly repeats structured data. The description does add real value beyond annotations by explaining what populates the queue and that disposition is a human decision, which shapes how the agent should behave after calling it.

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 short sentences, front-loaded with purpose, then the read-only constraint, then the workflow expectation. No filler and nothing that should be moved earlier.

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?

No output schema exists, and the description usefully characterizes the returned items, so return-value burden is low. The one gap is that it frames the tool purely as 'waiting in the review queue' while status can also list approved/rejected/all records, leaving that capability unmentioned.

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 only 33% and the description adds no parameter meaning at all. 'limit' and 'status' carry no descriptions in either place, and the status enum's ability to return approved/rejected/all items is never mentioned, so the agent must infer filtering behavior from the schema alone.

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 ('List items waiting in the review queue') and immediately clarifies the queue's contents (auto-captured session summaries, records logged with suggested=true). Together with the workflow note about approving/rejecting, an agent can distinguish this from siblings review_approve and review_reject without opening any 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?

'Show them to the user; approving or rejecting is the user's decision' gives clear behavioral context: this tool only surfaces items and routes the decision to the human/review_approve/review_reject. It lacks an explicit named alternative or when-not condition, so it falls short of a 5.

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