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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing: no indication of inputs consumed, whether it evaluates or generates, side effects, permissions, or what the result looks like. Claims about a "prompt kit" and a "30-day support promise" describe the commercial bundle, not tool 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?

Short, but the space is spent on promotional filler ("Instantly generate," "no prompt engineering needed," "30-day support promise") instead of the one thing an agent needs: what the tool does. It is front-loaded with a mismatched domain claim rather than the actual operation.

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?

With one optional parameter and no output schema, the description still needs to say what a "check" produces and how it differs from the gen/tpl variants in the rd-review family. Instead it explains a product bundle, leaving the agent unable to determine the tool's output or role.

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 100% for the single optional "query" parameter, so the schema already explains it as an optional scoping input; this sets the baseline at 3. The description adds nothing about how the query scopes the analysis or what form it should take, so no credit above baseline is warranted.

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 largely restates the name ("review check tool") and wraps it in marketing language rather than saying what operation it performs. Worse, it frames the tool as a "restaurant & brand intelligence pack," which is a different domain from the R&D review family (rd-review-gen-tool, rd-review-tpl-tool, rd-review-check-tool) it actually belongs to, so an agent cannot tell it apart from its siblings.

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 statement of when to use this tool, no conditions or exclusions, and no mention of the sibling alternatives (rd-review-gen-tool, rd-review-tpl-tool, rd-prd-check-tool, etc.). Phrases like "no prompt engineering needed" are sales claims, not selection criteria.

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