zen_cookies

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

It describes the basic behavior of each operation but lacks details on side effects (e.g., clear removes all cookies for url or domain) and does not mention return formats or error handling. No annotations are provided to supplement.

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 brief, uses bullet points effectively, and front-loads the key operations. Every sentence adds value without unnecessary details.

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 the simplicity of the tool, the description lacks details on return values for get (e.g., list of cookies), error scenarios, and prerequisites. No output schema or annotations exist to compensate, leaving gaps for an 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?

The description explains the role of url, name, and value for set/remove but fails to document other parameters like secure, path, and domain, which are in the schema. With 0% schema coverage, the description should cover more 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 it handles cookie operations with four specific verbs (get, set, remove, clear). It is distinct from sibling tools like zen_clear_browsing_data, which clears all browsing data, not just 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 lists required parameters for each operation (e.g., set requires url+name+value) but does not provide when-to-use guidance or mention alternative tools for similar tasks like zen_storage.

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