browser_cookie_get

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

No annotations provided. Description mentions null return for absent cookie, which is helpful. However, no details on idempotency, side effects, or permissions. For a simple read operation, it is adequate but lacks depth.

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?

Single sentence with clear front-loaded action. Zero wasted words. Perfectly concise for the function's simplicity.

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 an output schema exists (context signal), return values are likely documented elsewhere. However, the description lacks explanation of the session_id parameter and error handling. For a simple getter, it is minimally complete but could be improved.

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 has 2 parameters with 0% description coverage. Description only mentions the 'name' parameter implicitly (cookie name), but completely omits the optional 'session_id' parameter. Does not add meaning beyond what the schema's field names imply.

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?

Description clearly states verb 'get' and resource 'single cookie by name', and specifies return behavior ('or null if absent'). Distinguishes from siblings like browser_cookie_list and browser_cookie_set.

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?

Implies usage when you know the cookie name, but does not explicitly state when to use this vs alternatives like browser_cookie_list or browser_cookie_get. No when-not or prerequisite conditions mentioned.

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