Get review feedback

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value by describing what comes back (structured notes with a comment projection plus rendered markdown). It does not say what happens when a review has no feedback yet, or whether output size is bounded, which keeps it off a 5.

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?

Two tight sentences with the core capability front-loaded and the routing hint second. Minor waste in "now including" (temporal versioning cruft) and "projection of the comments," which is jargon a caller must interpret.

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?

For a single-parameter read tool with no output schema and annotations already covering safety, the description covers purpose, return shape, and the key alternative. Slight gap on empty-state behavior and on how markdown content should be consumed, but nothing that would cause a mis-call.

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?

Only one parameter, and schema coverage is 100% with "the opaque review id" already documented in the schema. The description adds no format or sourcing detail for the id, so the schema carries the full burden and 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 ("Get a review's human feedback") and immediately qualifies the scope: structured notes plus a rendered markdown block, not raw comment threads. That scope statement is what separates it from the comment-oriented siblings, so an agent can identify the tool without opening the 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?

Explicitly routes the agent elsewhere when the intent differs: "For the full threads use list_comments." This names the exact overlapping alternative and the condition that selects it, which is the main ambiguity a caller would face among list_comments/get_comment/reply_to_comment.

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