add_cookie

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

The description lacks behavioral details beyond the basic action. It does not disclose whether adding a cookie overwrites existing cookies with the same name, if validation occurs, error handling, or impact on the browser session. With no annotations, the description carries full burden but provides minimal 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?

The description is a single concise sentence, front-loading the core purpose. However, it may be too brief given the tool's complexity; a slightly more informative sentence could improve conciseness without adding excessive length.

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 the tool has 8 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to cover parameter semantics, return behavior, side effects, or prerequisites. This is insufficient for a tool with such parameter count and potential complexity.

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?

The input schema has 8 parameters (name, value, path, domain, expiry, secure, httpOnly, sameSite) with 0% schema description coverage. The description does not explain or hint at the meaning or usage of any parameter beyond implying 'name' and 'value' are needed. This leaves the agent with no guidance on how to correctly set optional fields.

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 'Add' and resource 'browser cookie' with scope 'for the current page domain'. It is specific and unambiguous, but does not explicitly differentiate from sibling tools like delete_cookie or get_cookies, which have distinct purposes.

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 usage guidance is provided. The description does not mention when to use this tool (e.g., when needing to set a cookie before navigation or authentication) or when alternatives like delete_cookie or get_cookies would be more appropriate. No prerequisites or exclusions are specified.

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