import_cookies

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

Discloses that the tool imports cookies and restores sessions, implying a write operation, but does not detail whether it overwrites existing cookies, requires any special permissions, or has side effects. Given no annotations, the description provides moderate but incomplete behavioral insight.

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?

Two succinct sentences deliver the core purpose and parameter hints without redundancy. Every sentence contributes value.

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?

Covers basic functionality and required parameters but omits what happens during import (e.g., merge vs. replace), error conditions, and absence of output schema leaves agents guessing about return values.

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 100%, so the description's mention of 'JSON string array' for cookies and 'userId' requirement adds no new information. It does not clarify the format of the cookie array or the purpose of 'tabId' beyond what the schema already states.

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?

Explicitly states 'Import cookies for authenticated sessions' with a clear verb and resource, and further explains it restores login sessions without re-authentication. It is distinct from all sibling tools, none of which directly handle 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?

Lacks guidance on when to use this tool versus alternatives like 'load_profile' or manual authentication. No mention of prerequisites beyond 'Requires userId', and no exclusions or negative cases.

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