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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered, but the description adds the decisive behavioral fact the annotations cannot convey: the tool returns textual guidance rather than performing the mutation, and "opens nothing by itself." It also explains why browser tools are required ("17hats publishes no public API"), though it does not mention any auth/connection requirement or what happens if no Cloud Browser session exists.

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?

Three tight sentences, each carrying distinct information: what is returned, that no action is taken, and the follow-up tool set. The only structural weakness is ordering — the misleading action-sounding clause is front-loaded ahead of the clarifying one, and the trailing "17hats's official API: 17hats publishes no public API" is slightly clunky phrasing.

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 explaining the return value, and it does so concretely ("screens, buttons, fields"). Combined with the annotations covering safety and the explicit handoff to cotlet_browser_* tools, an agent has enough to call it correctly; only the lack of any precondition or session-state detail keeps it from being fully complete.

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 semantics to elaborate and the baseline of 4 applies. Nothing in the description is needed to disambiguate inputs, and it correctly implies the tool is called with no arguments.

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 the specific resource (recording a payment in the user's own 17hats account) and, crucially, states that the tool "Returns how to do it in 17hats step by step (screens, buttons, fields) and opens nothing by itself" — which distinguishes it from the cotlet_browser_* action tools. The deduction is that the opening clause reads as though the tool performs the payment, and the clarifying correction only arrives in the second sentence, so an agent skimming could misclassify it as a write 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?

It explicitly routes the agent to the alternative: "then do it with the cotlet_browser_* tools in the user's 17hats Cloud Browser," which gives a clear this-then-that workflow. It stops short of stating when not to call it (e.g., if the agent already knows the 17hats flow) or any prerequisite such as an authenticated Cloud Browser session.

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