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

Annotations already declare readOnly, idempotent and non-destructive, and the description reinforces this with 'opens nothing by itself', so there is no contradiction. It adds genuinely useful context beyond annotations: the exact return content (steps/screens/buttons/fields) and the fact that DusterBook has no API, webhooks, Zapier app or Google Calendar/QuickBooks sync, which steers the agent away from a dead-end API search. The odd future-dated provenance is minor clutter but harmless.

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 disambiguation ('opens nothing by itself') is buried mid-sentence after a misleading opening verb, so the structure is not front-loaded. The 'from ChatGPT, Claude or any AI agent' clause and the trailing API/Zapier/QuickBooks paragraph are tangential padding that could be trimmed or moved to a caveat.

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 and no output schema, the description carries the return value on its own and does so ('Returns how to do it in DusterBook step by step'), plus the handoff to the browser tools. The main residual gap is that it does not say what happens if the user has no DusterBook account or lack access, though 'the user's own DusterBook account' hints at that requirement.

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 imposes no documentation burden and the baseline is 4. The description does not need to explain inputs, and appropriately spends its words on the return value and the follow-up browser step instead.

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 specifically that the tool returns a step-by-step procedure ('screens, buttons, fields') and 'opens nothing by itself', which is precise about the actual deliverable. It is slightly weakened by the opening clause 'Create quote in the user's own DusterBook account', which frames the tool as doing the creation even though it only returns instructions — the correction comes later in the same sentence. It also does not name the closest siblings (dusterbook_create_invoice, cotlet_app_guide) to differentiate itself.

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 an explicit two-step usage pattern: call this to get the procedure, 'then do it with the cotlet_browser_* tools in the user's DusterBook Cloud Browser'. That routes the agent to the correct execution tools. It stops short of stating when NOT to use it or how it differs from the other DusterBook creation tools.

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