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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world. The description adds real context beyond them: it opens nothing by itself, it returns screens/buttons/fields, and execution must happen through the Cloud Browser. The note that Podium has an official REST API but no official MCP server explains why this workaround exists.

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 core behavior is front-loaded, but the sentence about the official REST API and MCP server status is tangential to invoking the tool and lengthens an otherwise short description. Phrasing such as 'Returns how to do it in Podium step by step' is awkward and could be stated more directly.

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 guide tool, the description covers what it returns (step-by-step procedure), what it does not do (open anything), and what the agent should do next (cotlet_browser_* tools). Only the exact shape of the returned guidance is left unspecified, which is minor.

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 schema carries nothing to interpret and there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies no inputs are needed.

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 ('List reviews in the user's own Podium account') and immediately clarifies the non-obvious behavior: it returns step-by-step instructions rather than data. The sibling differentiation is partial — it points to the cotlet_browser_* family as the executor but never contrasts with podium_reply_to_review or other review-related 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?

Gives a clear two-step workflow: call this to get the procedure, then execute it with cotlet_browser_* in the user's Podium Cloud Browser. It does not state exclusions or when a different review tool (e.g. podium_reply_to_review) is the better choice, so guidance is strong but not complete.

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