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

With readOnlyHint=true and destructiveHint=false already declared, the description usefully confirms and adds meaning: it "opens nothing by itself" and returns a step-by-step walkthrough (screens, buttons, fields). That tells the agent the call is a non-mutating planning step, which is the key behavioral fact. It stops short of describing the shape/length of the returned instructions.

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 third sentence is a tangential API-availability note (REST API, API key location, "no official MCP server, checked 22 Oct 2026") that has no bearing on invoking this tool and dilutes the actionable content. The genuinely useful facts (returns instructions, opens nothing, use cotlet_browser_* next) are split across a run-on second sentence.

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?

There is no output schema, so the description does need to convey the return value — and it does, at a high level (step-by-step screens, buttons, fields). With zero parameters and clear annotations, that is close to sufficient, but the reader must reverse-engineer that this is a guide tool from a misleading first clause, and no guidance is given on the relationship to cotlet_app_guide.

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 the description introduces no phantom inputs or confusing expectations about arguments. There is nothing to mis-specify, so this dimension is essentially satisfied by default.

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 opening sentence reads as if the tool performs the reply ("Reply to a lead in the user's own Mailshake account from ChatGPT, Claude or any AI agent"), and only the second sentence clarifies that it actually returns step-by-step instructions. The real function — a how-to guide generator — is buried rather than front-loaded, so the purpose is recoverable but not stated crisply.

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 does say what to do next ("then do it with the cotlet_browser_* tools in the user's Mailshake Cloud Browser"), which is real routing guidance. However, it never distinguishes this from cotlet_app_guide or explains when an agent should call this guide versus acting directly, so the when/when-not is only implied.

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