interceptor_browser_get_cookie

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

The description notes a 'hard cap to keep output bounded', which signals potential truncation, but lacks details on side effects, authentication needs, or error handling. Since no annotations are provided, the description should carry more behavioral context.

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, front-loaded sentence with a parenthetical qualifier. It is concise and contains no superfluous information.

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 has 3 parameters, no output schema, and no annotations, the description covers the core purpose and a key behavioral constraint. It could mention what happens if the cookie_id is invalid or the cap is exceeded, but overall it is sufficient for basic use.

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?

All three parameters are fully described in the input schema (100% coverage). The description adds a general note about the hard cap but does not elaborate on parameter-specific semantics beyond the schema.

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 'Get one cookie by cookie_id', specifying the verb (get) and resource (cookie), and adds a constraint about a hard cap. It distinguishes from sibling tools like interceptor_browser_list_cookies which returns multiple 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 description implies use when a specific cookie's full value is needed, but it does not explicitly state when to use this tool versus alternatives (e.g., list_cookies for multiple, or get_storage_value for other storage). No when-not or alternatives are given.

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