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

The description explicitly discloses the key behavioral fact an agent needs — that the tool performs no side effects ('opens nothing by itself') and returns instructional text rather than executing a payment — which is consistent with readOnlyHint=true. It adds useful context on the absence of a public Dubsado API, though the dated claim is unverifiable here and it says nothing about prerequisites such as an active Cloud Browser session.

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 critical clarification ('returns steps, opens nothing by itself') is buried mid-sentence after a marketing-style opener listing ChatGPT, Claude 'or any AI agent'. Restructuring to lead with 'Returns step-by-step instructions for recording a Dubsado payment; performs no action' would cut a meaningful amount of low-value wording.

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, read-only guide tool with no output schema, the description covers what it returns, that it has no side effects, and which sibling tool family completes the task. It is nearly complete; only prerequisites (browser session, being logged in) and what to do if the guide's steps cannot be executed are unaddressed.

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 explain; the baseline of 4 applies. The description correctly implies a parameterless guide with no input to supply.

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 makes clear this is a guide generator, not an executor: it 'Returns how to do it in Dubsado step by step (screens, buttons, fields) and opens nothing by itself.' That distinguishes it from actual Dubsado action tools like dubsado_send_invoice. However, the opening clause 'Record payment in the user's own Dubsado account' reads like a mutation and briefly muddies what the tool actually does.

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 concrete workflow guidance: call this to get the steps, then perform them with cotlet_browser_* tools in the user's Dubsado Cloud Browser. It does not explain when to prefer a direct Dubsado API-style sibling (e.g., dubsado_send_invoice) or what to do if no browser session is available, so exclusions are implicit rather than stated.

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