cdp_set_cookies

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

No annotations are present, so the description must carry the burden. It reveals that cookies are written to the browser context of the session, but does not explain whether existing cookies are overwritten, whether the operation is destructive to other cookies, or what happens if the session is invalid. These behavioral details are critical for a mutation tool.

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 a single, direct sentence with no wasted words. It is concise and front-loaded, though it sacrifices informational depth; still, it earns its place as a brief overview.

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?

With no output schema and no annotations, the description is too sparse to be contextually complete. It lacks behavioral expectations (e.g., overwrite semantics, session requirements) and does not explain the cookie object structure, leaving significant gaps for the agent.

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 only 50% (only session_id has a description; the cookies array's nested fields are undocumented). The description adds no meaning beyond the schema, failing to compensate for the missing parameter explanations, such as the role of path, secure, or httpOnly in the cookie objects.

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 uses the specific verb 'Write' and clearly identifies the resource ('cookies onto the browser context of this session'). This distinguishes it from sibling cdp_get_cookies, which reads cookies, making the purpose unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that a session must be active (via cdp_connect) or that it should be used instead of cdp_get_cookies for writing. Usage is only implied by the tool name and description.

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