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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false; the description reinforces this consistently by stating it opens nothing and changes nothing. It also discloses the return shape at a high level (step-by-step screens, buttons, fields) and points to the browser tools that perform the actual mutation. The trailing paragraph about Method CRM's REST API and the absence of an official MCP server is informational but adds little behavioral clarity for invocation.

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 purpose and the follow-up path are front-loaded and earn their place. However, the closing paragraph about Method CRM's official API and a dated verification ('checked 23 Oct 2026') is tangential to selecting or invoking this tool and dilutes the message.

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, no-output-schema guidance tool whose safety profile is already covered by annotations, the description supplies what an agent needs: what it returns, that it has no side effects, and which sibling tools complete the job. Missing only explicit exclusions or a note on what the returned steps look like when the workflow cannot be completed.

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 nothing for the description to disambiguate and the baseline of 4 applies. No misleading claims are made 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 names a specific verb and resource (convert an estimate to an invoice in Method CRM) and, crucially, discloses that the tool only returns step-by-step instructions and 'opens nothing by itself'. This distinguishes it from the action-performing cotlet_browser_* siblings. The opening clause still reads like a write action, so an agent skimming could momentarily mistake it for the real conversion.

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 two-step usage pattern: call this to learn the screens/buttons/fields, then execute with the cotlet_browser_* tools in the Cloud Browser. That is actionable routing guidance. It does not state when not to use it (e.g., when the user just wants a list of estimates or an already-known workflow).

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