cookies_set

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

No annotations are provided, so the description carries the full burden. It describes the input format and purpose but does not disclose whether cookies replace or append to existing ones, persistence across navigations, or error handling. The mention of bypassing bot detection adds context, but more behavioral detail would improve transparency.

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 concise sentences: first states action and format, second provides a key use-case. No unnecessary words or redundancy.

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 no output schema and minimal annotations, the description provides sufficient context for an agent to understand the tool's purpose and when to invoke it. It could be enhanced with details on cookie persistence or side effects, but overall it is complete enough for effective use.

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% with descriptions for both parameters. The description adds detailed structure for cookie objects (e.g., name, value, domain, etc.) and notes that each item can also be a raw Set-Cookie string, providing meaning beyond the schema's generic 'array' type.

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?

Description clearly states that the tool adds cookies to the session jar, specifies input formats (object or Set-Cookie string), and provides a concrete use case (replaying clearance cookies). It distinguishes itself from sibling tools like cookies_get and cookies_clear.

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?

Description explicitly states when to use (to replay clearance cookies from a real Chrome session to bypass bot detection). While it doesn't mention when not to use or list alternatives, the given scenario is specific and actionable.

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