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

Beyond the readOnly/idempotent annotations, the description explicitly says it 'opens nothing by itself' and that its output is screens/buttons/fields instructions, which tells the agent this is an informational, no-side-effect call whose real effect comes from later browser tools. It also scopes execution to the user's own BrightLocal account, adding auth context not in the annotations.

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 the browser-tool handoff are front-loaded and earn their place, but 'from ChatGPT, Claude or any AI agent' is filler and the closing sentence about BrightLocal's REST API and 'BrightLocal Anywhere' MCP server reads as promotional background with no bearing on selecting or invoking this 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?

For a zero-parameter, read-only guide tool with full annotation coverage, the description covers the essentials: what it returns and what to do next. What it omits is the disambiguation the agent most needs — how this differs from the identically named sibling report tools and when each should be called.

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 no parameter meaning to add; the baseline for a parameterless tool applies. Nothing in the description misleads about inputs.

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 verb and resource (local search grid report) and, crucially, clarifies that it returns step-by-step instructions rather than the report data itself. However, it never differentiates itself from the near-identically named sibling get_local_search_grid_report or brightlocal_get_rank_tracker_report, leaving ambiguity about which one actually fetches data.

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 a clear downstream workflow ('then do it with the cotlet_browser_* tools in the user's BrightLocal Cloud Browser'), which is genuinely useful sequencing information. But it never says when to choose this guide tool over the API-style sibling tools that share almost the same name, so the agent still has to guess at the routing.

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