save_cookies

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

No annotations, so the description carries the full burden. It does not say whether an existing file is overwritten, whether it requires an active browser session, whether the write can fail or what the file contents look like. For a filesystem-mutating tool this is a real gap.

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?

A single short sentence with no filler; the action and destination are front-loaded. Nothing to trim.

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?

Output schema existence excuses explaining return values, but the definition is thin for its complexity: one undocumented parameter, no annotations, no session/file behavior, and no relation to load_cookies. An agent would have to guess at path semantics.

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?

There is one parameter ('path') with 0% schema description coverage and a default of empty string, yet the description never mentions it. The agent cannot tell from the description what happens when path is omitted, nor what format the path should take.

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?

Specific verb ('save') plus resource ('cookies of the current session') plus output format ('JSON file'). It implicitly contrasts with the sibling load_cookies, but never names it explicitly, so the sibling differentiation is left to inference.

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 statement of when to use this tool, when not to, or that load_cookies is the inverse operation for restoring a saved session. The agent gets the what but not the when.

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