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

Annotations already flag destructiveHint=true, openWorldHint=true and idempotentHint=false, but the description adds material context they cannot carry: it returns the resulting URL and title, card fields and account pages are refused, each started minute of the session costs credits, and the session expires on close or 3 minutes after the last call. That cost/lifetime disclosure is exactly what an agent needs before committing. It doesn't explain what state change makes the call destructive.

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?

Front-loaded with the verb and resource, then the mechanics, then refusals and cost. The billing/session sentence reads as boilerplate shared across the cotlet_browser_* family but still earns its place for a paid, self-expiring session.

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?

No output schema exists, yet the description states the return value (URL and title), the refusal cases, and the session lifetime, so an agent can call it safely. The one gap is that it doesn't say the element list must first be obtained via cotlet_browser_read, which is the prerequisite an agent is most likely to miss.

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?

Schema coverage is 100%, so baseline is 3. The description does add one genuinely useful clarification the schema lacks — that the option may be given as the label as the element list displays it or by its value — but the element parameter is left to the schema's own wording.

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 — choose an option of a drop-down list — scoped to the current page in the user's Pirate Ship Cloud Browser, and identifies the two coordinates (list number in the element list, option label or value). This distinguishes it cleanly from cotlet_browser_click, cotlet_browser_type, and cotlet_browser_press, which act on other element kinds.

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 a real exclusion set: card fields and account pages are refused, which tells the agent where not to aim this tool. It does not name the alternative (e.g. use cotlet_browser_read first to get the element list, or click instead when the widget isn't a native select), so routing is implied rather than explicit.

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