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

Beyond the annotations (readOnlyHint, idempotentHint, openWorldHint=false), the description adds meaningful behavior: the tool itself opens nothing and merely returns step-by-step UI instructions, with the real action delegated to the browser tools. It also discloses the API situation (official REST v4 with OAuth 2, no official MCP server) which is useful for planning. It doesn't say how the output is structured beyond "step by step," which prevents a 5.

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 guidance is front-loaded and clear, but the API sentence ("Podium has an official REST API (v4, OAuth 2) but no official MCP server (checked 23 Oct 2026)") is somewhat tangential and the dated check is verbose. The wording "Returns how to do it in Podium step by step (screens, buttons, fields)" is a bit awkward but informative. Overall it is reasonably tight but not maximally economical.

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 guidance tool, the definition covers purpose, the follow-up mechanism (cotlet_browser_*), and the fact that it performs no action itself. No output schema exists, and the description notes the step-by-step return nature. It could be more explicit about what the returned instructions look like, but it is complete enough to call correctly.

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 and there is nothing for the description to clarify. No param-level ambiguity exists.

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 states a concrete verb and resource ("List conversations in the user's own Podium account") and scopes it clearly. It distinguishes itself from the cotlet_browser_* tools by saying it only returns step-by-step instructions and opens nothing itself. It does not explicitly differentiate from sibling podium_* tools like podium_send_message, but the purpose itself is unmistakable.

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?

Usage is clear: call this to learn how to list conversations, then perform the action with cotlet_browser_* in the user's Podium Cloud Browser. The when-to-use and the follow-up are both specified. There is no explicit when-not-to-use statement or comparison to the other podium_* siblings, which keeps it short of a 5.

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