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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'opens nothing by itself', so there is no contradiction. It adds real behavioral context beyond the annotations by specifying the return content (screens, buttons, fields) and the follow-up tool family to use. The trailing note about AccuRanker's official API and MCP server is unexplained and adds noise rather than behavioral clarity.

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 purpose and the workflow handoff are front-loaded and efficient, but the closing sentence about the official API and official MCP server ('checked 23 Oct 2026') is ambiguous — it is unclear whether it is a warning against using this tool or just a footnote. That sentence does not earn its place and slightly muddies the call decision.

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 input schema and no output schema, the description carries the full burden, and it does explain the return shape (step-by-step screens/buttons/fields). However, it never explains how the target competitor is identified given that the tool accepts no arguments — the agent is left to guess whether it comes from conversation context. That is a meaningful gap for a tool whose whole job is producing instructions for a specific competitor.

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 and schema coverage is 100%, so the baseline of 4 applies. There is no parameter meaning the description could add.

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 (a competitor in the user's AccuRanker account) and, importantly, clarifies that the tool does not perform the action but returns step-by-step instructions. That resolves the tension between the action-verb name and the read-only behavior. It does not explicitly contrast itself with sibling add_* tools (add_domain, add_keywords), so differentiation relies on the name alone.

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 handoff: call this to get the steps, then perform them with cotlet_browser_* tools in the AccuRanker Cloud Browser. That is an explicit workflow routing statement rather than implied usage. It stops short of saying when NOT to use it (e.g., when the official AccuRanker API/MCP path is preferred, which it mentions but never resolves).

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