Set Browser Cookies

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

Annotations indicate readOnly false, destructive true, and open world. The description adds context about credential handling and secrecy, enhancing transparency without contradicting annotations.

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 description is concise with no unnecessary words, front-loaded with purpose. It could be slightly more structured but is effective.

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?

Given moderate complexity and an output schema, the description covers preconditions and sensitivity but lacks details on behavior like overriding cookies or return values, leaving 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 description coverage is 0%, but the description does not detail the cookies array or its properties. It mentions the acknowledge flags as preconditions, which adds some meaning, but fails to fully compensate for the lack of schema descriptions.

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 the tool establishes or changes cookie state, aligning with its name and title. However, it does not explicitly distinguish from sibling tools like browser_import_storage_state that may also set cookies.

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 says when to use this tool ('full-profile authorized test requiring establishing or changing cookie state') and lists required preconditions. It does not mention alternatives, though the context is clear.

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