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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond them by stating it 'opens nothing by itself' — i.e., no external call or browser session is started — and by naming the follow-up tool family required to actually perform the task.

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?

The mechanics and follow-up instructions are front-loaded in the first two sentences with little waste. The final sentence about REVIEWS.io's official API is mildly tangential context, and the audience phrase 'from ChatGPT, Claude or any AI agent' is filler, but neither is harmful.

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 guidance tool, an agent needs to know what comes back (step-by-step screens/buttons/fields) and what to do next (cotlet_browser_*), both of which are stated. The only residual gap is that the description never clarifies whether any invitation data is also returned.

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 there is no parameter semantics to add; the baseline for a parameterless schema is 4. Nothing in the description is needed to understand the (empty) input object.

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 opening sentence 'List invitations in the user's own REVIEWS.io account' reads as if the tool retrieves invitation data, but the next sentence reveals it actually returns step-by-step UI instructions and performs no action. That reversal makes the tool's real purpose (a guidance generator, not a data lister) clear only on careful reading, and it never differentiates itself from siblings like reviews_io_pause_invitations.

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?

It states a clear workflow: call this first, then execute the steps with cotlet_browser_* tools inside the REVIEWS.io Cloud Browser. The API note (REST API only on Plus plan, no official MCP server) implicitly explains why the browser path is required, though no explicit when-not-to-use condition is given.

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