browser_cookie_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 for behavioral disclosure. It only states 'Set a cookie' without mentioning whether existing cookies are overwritten, if a session is required, or any side effects. This is insufficient for an AI agent to understand the tool's behavior safely.

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 very short (one sentence), which is concise, but it lacks structure. It could benefit from a brief note on prerequisites or parameter grouping. It is front-loaded with the purpose, but the brevity means some needed information is missing.

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?

Despite having an output schema and a simple operation, the description fails to cover all 6 parameters (only mentions url and domain+path) and does not explain the role of session_id or the expected behavior. It feels incomplete for an AI agent to use correctly.

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%, so the description must add meaning. It explains the url vs domain+path relationship but does not describe the 'name', 'value', or 'session_id' parameters. The schema itself shows they are required or optional, but the description adds little beyond the schema for most parameters.

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 verb 'Set' and the resource 'cookie', and it distinguishes between two methods of specifying the cookie location (url vs domain+path). This is specific and helps differentiate from sibling tools like browser_cookie_delete or browser_cookie_get.

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 tells when to use the tool (to set a cookie) and provides a choice of input formats. It does not explicitly state when not to use it or mention alternatives, but given the context of sibling tools, the guidance is clear enough for a simple operation.

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