browser_cookies_get

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

No annotations are provided, so the description carries the full behavioral burden. It implies a safe read, but says nothing about whether the domain parameter narrows results, required permissions, or how the operation interacts with the session. An output schema exists, so return format need not be described, but the behavioral profile is thin.

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 front-loaded sentence with no wasted words and the scope stated up front. It is efficient, though its brevity is partly a symptom of under-specification rather than disciplined editing.

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 structure is covered by the output schema, but with three parameters at 0% schema description coverage and no annotations, the description leaves too much unstated: no domain filtering meaning, no session semantics, no behavioral notes. For a tool whose structured fields say almost nothing, this is inadequate.

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%, so the schema documents no meaning for session_id, domain, or timeout_seconds. The description mentions no parameters at all, and its phrase 'all cookies' actively obscures the fact that domain can filter the result set, leaving an agent unable to infer parameter behavior.

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 specific verb (Get), resource (cookies), and scope (visible to current browser context), so an agent can tell it reads rather than writes cookies. It does not explicitly differentiate itself from siblings like browser_cookies_save or browser_cookies_clear, but the read-vs-mutate distinction is inferable from the name and wording.

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 gives no when-to-use context, no prerequisites, and no mention of alternatives such as browser_cookies_save for persistence or browser_storage_get for other storage. The scope phrase 'current browser context' is informative but is not usage guidance.

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