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

Annotations already establish readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral value by clarifying that the call performs no UI action on its own ("opens nothing by itself") and that the deliverable is procedural instructions covering screens, buttons, and fields. It does not describe the response shape beyond that, but the key behavioral trait is disclosed.

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 — that this returns instructions and requires follow-up browser tool calls — is buried mid-sentence after a misleading lead clause. The closing sentence about BrightLocal's REST API and official MCP server is marketing context that does not help an agent decide or invoke, so it does not earn its place.

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 read-only guidance tool the description is broadly sufficient, and it names the follow-on cotlet_browser_* tools. It is still incomplete on the point that matters most for routing: how it relates to the sibling list_reviews and cotlet_app_guide, and what prerequisites (BrightLocal Cloud Browser session, account connection) must exist before the guidance is usable.

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 baseline is 4. The description correctly implies no inputs are required, and nothing it says about parameters is misleading or missing.

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 does eventually disclose that this tool returns step-by-step guidance for listing reviews rather than the reviews themselves ("Returns how to do it in BrightLocal step by step ... opens nothing by itself"). However, it opens by claiming to "List reviews in the user's own BrightLocal account," which contradicts the actual behavior, and it never distinguishes itself from the sibling tool literally named list_reviews. An agent could easily pick the wrong one.

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 implied rather than stated: the agent is told to "do it with the cotlet_browser_* tools in the user's BrightLocal Cloud Browser" after reading the guidance. There is no explicit condition for choosing this tool over list_reviews (the direct API listing) or over cotlet_app_guide, and no when-not guidance at all.

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