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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safe-read profile is covered. The description adds material context beyond that: it explicitly says it 'opens nothing by itself', discloses the return shape (screens, buttons, fields), and notes Pirate Ship has no official API. That prevents the common failure of an agent assuming the call itself fetches live rates.

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 operative content (returns a procedure, does nothing itself, follow up with cotlet_browser_*) is present and reasonably front-loaded, but the lead clause 'from ChatGPT, Claude or any AI agent' and the parenthetical 'checked 11 Oct 2026' are noise that do not help an agent decide or invoke. Two of four sentences could be trimmed without loss.

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, no-output-schema guide tool, the description covers everything needed: what it returns, that it causes no side effects, and which tools complete the task. It even preempts the 'why not use the API' question by stating no API exists.

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 nothing for the description to disambiguate and the baseline applies. It correctly avoids inventing parameter talk.

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?

States a specific verb and resource (get rates in the user's Pirate Ship account) and immediately clarifies the non-obvious part: this returns step-by-step instructions rather than performing the lookup. That distinguishes it from the cotlet_browser_* executors by name. The opening clause about ChatGPT/Claude/AI agents is filler that dilutes rather than sharpens the purpose.

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?

Gives clear sequencing guidance: call this to get the procedure, then execute it with cotlet_browser_* tools in the Pirate Ship Cloud Browser. It stops short of naming when NOT to use it versus sibling flows like pirate_ship_buy_labels_in_bulk or cotlet_app_guide, so the routing is implied rather than exhaustive.

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