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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description reinforces this with 'opens nothing by itself', so behavior is consistent and confirmed. It also discloses the return shape qualitatively (screens, buttons, fields), though it omits anything about failure cases if the account is not connected.

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 and next step are front-loaded and useful, but the closing sentence about Judge.me's REST API, private token, OpenAPI file, and the dated 'no official MCP server' check adds context an agent cannot act on and dilutes the payload.

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 with no output schema, the description covers what it returns, what it does not do, and how to proceed afterwards. Only the relationship to the sibling reply-sending tools is left unstated.

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 parameter-specific the description needs to compensate for.

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 clearly states the tool returns step-by-step instructions for replying to a review in Judge.me rather than performing the reply itself, which corrects a potentially misleading name. It does not, however, distinguish itself from the sibling judge_me_send_private_reply, leaving ambiguity about which tool actually sends a reply.

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 explicit follow-through guidance: use this for the instructions, then act with the cotlet_browser_* tools in the user's Judge.me Cloud Browser, and it scopes the target to the user's own account. There is no explicit when-not guidance or comparison against the sibling write tools.

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