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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value beyond them: it says the tool 'opens nothing by itself', that the payload is step-by-step UI instructions, and that DusterBook publishes no API, webhooks or Zapier app and does not sync with Google Calendar or QuickBooks — which explains why browser automation is the only path.

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 sentences, front-loaded with the action and immediately followed by the key caveat and the next-step routing. The phrase 'from ChatGPT, Claude or any AI agent' is promotional filler and the 'checked 9 Nov 2026' date stamp is noise, but neither obscures the operational content.

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 burden of explaining what comes back, and it does: step-by-step screens, buttons and fields, plus the explicit handoff to cotlet_browser_* tools. The only gap is that it does not describe the shape or granularity of those returned instructions, which is minor for a zero-argument guide tool.

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 and the schema is an empty object with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter detail is missing.

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 opening sentence frames the tool as 'List booking requests', but the second sentence reveals it actually 'Returns how to do it in DusterBook step by step (screens, buttons, fields) and opens nothing by itself'. The real purpose (returning instructions rather than data) is disclosed but sits in tension with the name and title, so an agent must read past the first clause to learn what it really 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?

The description explicitly routes the agent onward: after getting the steps, 'do it with the cotlet_browser_* tools in the user's DusterBook Cloud Browser'. That is a concrete alternative and the condition that selects it. It stops short of stating when not to call this tool, which keeps it below a 5.

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