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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so safety is covered. The description does add genuinely non-obvious behavior: it opens nothing and returns instructions only, and the note that Pirate Ship has no API explains why the browser path is required. It stops short of saying what the returned guide actually looks like or its size.

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 purpose is front-loaded in the first sentence and the most important caveat ('opens nothing by itself') follows immediately. The wording is dense, with semicolon-chained clauses and a dated parenthetical, but nearly every clause carries decision-relevant information.

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 guide tool with no output schema, the description covers what it returns, what it does not do, and the follow-up tool family. The only gap is the absence of detail about the shape or length of the returned walkthrough, which an agent might want to know before calling it.

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?

There are zero parameters and no schema to mine, so the baseline is 4. The description correctly implies the tool needs no input, matching the empty object schema.

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 that this tool does not buy anything itself but returns a step-by-step walkthrough (screens, buttons, fields), which resolves the misleading verb in the name. It is distinguishable from the cotlet_browser_* siblings it delegates the actual work to, though it never contrasts itself with cotlet_app_guide.

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 describes a workflow sequence — get the steps here, then execute them with cotlet_browser_* tools in the Pirate Ship Cloud Browser — which is useful implicit usage guidance. However, it never states when to choose this over cotlet_app_guide or pirate_ship_get_rates/import_orders, nor any precondition such as being logged in.

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