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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: it returns procedural detail (screens, buttons, fields) and performs no side effect itself, plus notes the absence of an official Judge.me MCP server. It does not describe output shape, but that is minor here.

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 disambiguation ('opens nothing by itself') is buried mid-sentence inside a long clause rather than front-loaded, which risks an agent skimming it as an action tool. The closing sentence about Judge.me's REST API and missing MCP server is background context that does not help invoke the tool and could be trimmed.

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 no parameters and no output schema, the description carries the full burden of explaining the return value, and it does so concretely (step-by-step screens, buttons, fields). It is complete enough for an agent to know what comes back and that no action occurs, though it could state the format of the returned guidance more precisely.

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 absence of arguments is consistent with a guidance-returning tool.

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 specific resource and outcome: it returns step-by-step Judge.me publishing instructions (screens, buttons, fields) and explicitly says it 'opens nothing by itself.' That is clear, though the name 'publish_review' promises an action the tool does not perform, so the agent must read past a misleading label to learn the tool is advisory only.

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 routes the agent explicitly: call this to get instructions, then execute with the cotlet_browser_* tools in the Cloud Browser. It supplies clear context for use and names the alternative tool family, but gives no when-not guidance relative to siblings like judge_me_list_reviews or judge_me_reply_to_review.

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