Manage Cookies

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

Goes well beyond the annotations by disclosing that save can overwrite files, that load does not guarantee login restoration, that cookies may be expired or domain-restricted, and that cookie data may contain credentials. The security warning and per-action return behaviors add substantial context beyond openWorldHint and idempotentHint.

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 long but well-structured with clear sections for actions, returns, security, and notes. Each sentence earns its place, and the most important high-level purpose is front-loaded.

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?

Complete for a two-parameter tool with no output schema. It covers all actions, parameter behavior, return types, file-overwrite risk, security concerns, and limitations of load. An agent has everything needed to invoke the tool 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%, but the description fully compensates by explaining each enum value, defining the filename parameter's role for save/load, and noting it is ignored for get_all and clear. This adds meaning the schema alone does not provide.

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?

States a clear verb and resource: 'Manage cookies for the current browser session' and enumerates the four concrete actions (inspect, clear, save, restore). This clearly differentiates it from sibling tools like manage_storage or manage_history.

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 explains when cookie management is useful: inspecting session state, preserving logins between runs, restoring sessions, and resetting website state. It does not explicitly name sibling alternatives or provide when-not-to-use guidance, but the context is clear enough for an agent.

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