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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description usefully reconciles the misleading 'Send' name with those hints by stating 'opens nothing by itself'. It also discloses the return shape (step-by-step screens, buttons, fields) and the reason browser automation is required (no public Dubsado API), which is context annotations cannot carry.

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 behavior and next step are front-loaded, but the closing 'Dubsado's official API: Dubsado has no public API (checked 11 Oct 2026)' is awkwardly phrased and carries a date that reads as future-dated, adding noise. The parenthetical '(screens, buttons, fields)' is efficient and earns its place.

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 comes back, that nothing is mutated, and which tools perform the actual work. The only gap is that it does not say whether the guide is tailored to a specific invoice or is generic.

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 baseline is 4; there is nothing for the description to disambiguate. It correctly avoids inventing inputs and instead describes what the call yields.

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 concrete resource and task (sending an invoice in the user's Dubsado account) and then clarifies the actual mechanics: it returns step-by-step instructions rather than performing the send. That correction of the name's action framing is valuable, but it never distinguishes this from the sibling dubsado_send_form, which likely has an identical guide-shaped contract.

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 operating sequence: call this first to get screens/buttons/fields, then execute with the cotlet_browser_* tools in the Dubsado Cloud Browser. There is no explicit when-not guidance (e.g., when to prefer dubsado_list_unpaid_invoices or record_payment instead), so it stops short of full routing.

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