get_live_cookies

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

No annotations are provided, so the description carries full burden. It mentions using a COPY of cookies/sessions, implying non-destructive behavior, but does not explicitly state safety, permissions, or side effects. Lacks disclosure of whether browser state is affected or if preconditions like an open browser are required.

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?

Two sentences, no waste. First sentence states core purpose, second explains the parameter. Effectively front-loaded and efficient.

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 simple tool with one optional param and no output schema, the description explains the parameter well. However, it does not describe the return format (e.g., list of cookie objects) or mention any prerequisites like the browser must be started. This leaves some gaps.

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 0% (only type string, no description). The description adds significant meaning by explaining the 'useProfile' parameter can be a profile name or empty string for default, and its effect (copy vs clean browser). This goes beyond the 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 clearly states 'Get cookies from the live browser context', specifying a retrieval operation. However, it does not differentiate from sibling tools like 'get_cookies' which may also retrieve cookies, missing explicit sibling differentiation.

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 provides clear context on when to set the 'useProfile' parameter (profile name or empty string for default, omit for clean browser). However, it offers no guidance on when to avoid this tool or alternatives, such as when to use 'get_cookies' instead.

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