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

With no annotations, the description must carry the behavioral burden, and it does disclose key traits: the link carries its own access (no local push/auth needed), it is not persisted into list_reviews, and the output is Markdown. It does not cover failure modes such as expired or malformed links, which is the remaining gap.

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 sentences, each carrying distinct information: what it does, when to use it, and its persistence behavior. Front-loaded with the action and output format, with no filler.

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 tool with no annotations and no output schema, the description covers purpose, routing, access model, and return format, which is nearly everything an agent needs. It stops short of describing behavior on invalid or expired links.

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 description coverage is 100%, so the schema already documents the url field and its ?t=… requirement. The description's mention of the '/r/<id>?t=…' URL shape restates rather than extends 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 ('open a design review from a share link') plus the return shape ('get its feedback as Markdown'). It also differentiates itself from list_reviews by noting the link stays out of the list, so an agent can choose between them without inspecting schemas.

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 states the trigger condition ('when the user pastes a review link rather than asking for their own reviews') and contrasts it with the sibling list_reviews. The note that the review need not have been pushed from this machine further clarifies when it applies.

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