load_cookies

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

The description carries the full burden since no annotations are provided. It states the action but does not disclose whether loading replaces existing cookies, whether it requires a specific file format, or what happens if the file is missing or malformed.

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, focused sentence with no unnecessary words. Every word, including 'previously saved,' adds relevant context about the tool's purpose and relationship to save_cookies.

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?

For a simple tool with one optional parameter and an output schema, the description is minimally adequate. However, it omits important behavioral context such as whether loading merges or replaces existing cookies and what constitutes a valid saved file, which an agent would benefit from knowing.

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%, and the description adds minimal meaning to the 'name' parameter beyond the schema's default value. It implies the parameter refers to a file, but it does not clarify the filename semantics, path handling, or format expectations.

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 uses a specific verb, 'load,' with a clear resource, 'cookies from a previously saved file.' This distinguishes it from siblings like save_cookies, which writes cookies to a file, and get_all_cookies, which retrieves current 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 phrase 'previously saved file' implies this tool is meant to be used after saving cookies, likely with save_cookies. However, the description does not explicitly state when to use it over alternatives or mention any preconditions or caveats.

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