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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description reinforces this with "opens nothing by itself," which resolves the apparent tension between the write-like verb "moderate" and the read-only annotation. It adds genuinely new context the annotations cannot carry: that REVIEWS.io's REST API is Plus-plan only and has no official MCP server, explaining why browser automation is the route. It does not describe the shape or length of the returned steps beyond screens/buttons/fields.

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?

Front-loaded with the purpose and the crucial "returns steps, opens nothing" correction, then the follow-up tooling, then API context. The API sentence is the longest and least immediately actionable, but it earns its place by justifying the browser-based approach. Slight verbosity in "checked 23 Oct 2026" is a minor cost.

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 zero-parameter, no-output-schema tool, the description covers what it returns (step-by-step screens, buttons, fields), what it does not do (opens nothing), and how to continue with cotlet_browser_*. The remaining gap is what to do if the Cloud Browser session is not open or the app is not connected, which an agent would have to discover elsewhere.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The description correctly implies no arguments are needed, since the call only produces guidance.

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?

Names a specific verb and resource ("Moderate review in the user's own REVIEWS.io account") and then corrects the natural reading by stating it "Returns how to do it in REVIEWS.io step by step." That clarification tells an agent this is a guidance tool rather than an executor. It stops short of distinguishing itself from siblings like reviews_io_reply_to_review or reviews_io_tag_reviews, which could also be read as forms of moderation.

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?

Gives a clear follow-up workflow: call this, then act with the cotlet_browser_* tools in the user's REVIEWS.io Cloud Browser. What is missing is selection guidance against alternatives — nothing says when to pick this over reviews_io_reply_to_review or the sibling moderation actions, and no prerequisites (e.g. an open browser session) are stated.

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