browser_get_cookies

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

The annotations already indicate read-only behavior (readOnlyHint: true). The description adds valuable transparency by detailing the return format (list of dicts with fields: name, value, domain, path, secure, httpOnly, expiry), which goes beyond the annotation and helps the agent understand the output.

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 extremely concise: two short sentences plus a bullet-like list of fields. Every sentence is informative and front-loaded with the action. No wasted words.

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?

Given the tool's simplicity (no parameters, no output schema needed beyond what description provides) and the presence of an output schema, the description is complete. It fully explains what the tool does and what it returns.

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?

The tool has zero parameters, so schema description coverage is 100%. The description adds no parameter information, but baseline is 4 as per guidelines. No additional clarity needed.

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 clearly states the verb 'Return', the resource 'all cookies', and the scope 'for the current page'. It distinguishes this tool from siblings as the only cookie retrieval tool among many browser actions.

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 provides a clear use case: 'Useful for inspecting authentication state or session tokens.' While it does not explicitly list when not to use or mention alternatives, the context is sufficient given the unique purpose of the tool.

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