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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description supplies the non-obvious behavioral fact an agent could not infer: this tool writes nothing and only returns procedural guidance, with a defined return shape (screens, buttons, fields). It also explains the API constraint (token only obtainable from RazorSync support), which justifies why the guide path exists. No contradiction with the read-only 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 clarification is front-loaded in the first sentence, which is good, but the second sentence is a semicolon-chained run-on and the third sentence about the token-based API and its 'checked 8 Nov 2026' date is lengthy supporting trivia rather than operational guidance. It is informative but not tightly edited.

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 zero parameters and no output schema, the description carries the burden of describing returns, and it does so at a high level (step-by-step screens, buttons, fields) plus the follow-up tool path. It stops short of stating the exact response format or what happens if the app/screen is not available, which would fully close the loop.

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 and the baseline of 4 applies. The description correctly implies no inputs are needed since it only returns instructions.

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?

States a specific verb and resource ('Record payment in the user's own RazorSync account') and immediately clarifies the actual mechanic: it 'Returns how to do it in RazorSync step by step (screens, buttons, fields) and opens nothing by itself.' This corrects the misleading tool name and separates it from the cotlet_browser_* siblings that perform the action.

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?

Explicitly routes the agent: get the steps here, 'then do it with the cotlet_browser_* tools in the user's RazorSync Cloud Browser,' which names the alternative action path. It does not spell out when NOT to use it (e.g., when the user wants a read-only lookup, where razorsync_list_customers or cotlet_get_call would apply), so it falls short of full when/when-not coverage.

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