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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description usefully reinforces this with 'opens nothing by itself', which explains why a tool named 'record payment' is read-only. Beyond that it adds little: no statement about whether the returned steps are user- or org-specific, whether a Method CRM login/session is required, or whether the guidance could go stale. The closing paragraph about Method CRM's REST API and the absence of an official MCP server is background rationale rather than behavior the agent must know before calling.

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 clarification (returns a procedure, opens nothing, execute via cotlet_browser_*) is compressed into one sentence, but it is preceded by a clause that restates the tool name and momentarily implies the opposite behavior. The trailing REST API / 'checked 23 Oct 2026' note is secondary justification that does not help the agent act and lengthens the definition without adding decision value.

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 parameters, no output schema, and annotations covering the safety profile, the description supplies what the agent most needs: what is returned (screens, buttons, fields) and what to do next (cotlet_browser_* tools). Minor gaps remain around prerequisites such as an authenticated Method CRM browser session and whether the steps are tailored to the user's account.

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 carries no semantics that the description needs to compensate for; the baseline for a no-parameter tool applies. The description adds no parameter-like detail, but none is required.

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 and outcome: it returns step-by-step instructions (screens, buttons, fields) for recording a payment in Method CRM rather than performing the action. The opening clause 'Record payment in the user's own Method CRM account' momentarily reads as if the tool performs the write, but the very next clause ('Returns how to do it in Method CRM step by step... opens nothing by itself') corrects that. It is clearly differentiated from the cotlet_browser_* siblings by naming them as the execution path.

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?

The definition gives explicit routing: call this tool first to get the procedure, then carry it out with the cotlet_browser_* tools in the user's Method CRM Cloud Browser. What is missing is any exclusion or preference statement relative to the other method_crm_* siblings (e.g., when to use list_overdue_invoices or send_invoice instead), but for a guidance tool the workflow context is clear.

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