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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description usefully confirms and explains that by stating the tool 'opens nothing by itself' and only returns instructions. It also discloses the required follow-up (browser tools) and the API-situation context for why no direct API path exists. It does not cover the browser-session prerequisite or how the returned steps are structured beyond a keyword list.

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 critical fact (no action is taken, instructions are returned) is front-loaded in the second sentence, which is good. However, 'from ChatGPT, Claude or any AI agent' is filler, and the trailing note about Podium's REST API and MCP server status is background justification rather than something needed to invoke the tool.

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 zero params and no output schema, the description carries the burden of explaining what comes back, and it does so at a high level ('step by step, screens, buttons, fields'). It also names the follow-on tools. What is missing is the precondition for that follow-on step, e.g. that a Podium Cloud Browser session must be opened first.

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 nothing for the description to disambiguate; baseline 4 applies. The description correctly makes no parameter claims, avoiding confusion about inputs the schema does not have.

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 name and first sentence frame this as 'Send review invite', but the second sentence corrects that framing: the tool returns step-by-step instructions ('screens, buttons, fields') and 'opens nothing by itself'. That distinction is specific and actionable, though an agent skimming the first line could still think this is the send action itself. It also positions the tool relative to the cotlet_browser_* family, which aids discrimination.

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 gives the workflow ('then do it with the cotlet_browser_* tools in the user's Podium Cloud Browser'), which is useful implied usage guidance. But it never states when to prefer this over siblings such as podium_reply_to_review or podium_list_reviews, nor any precondition like being logged into Podium before the browser step. Usage is inferable rather than explicit.

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