eight_set_cookie

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

No annotations provided, so description carries full burden. It discloses persistence ('local MCP config file') but omits details like overwrite behavior, side effects, or security implications. The 'verify' parameter is not explained.

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 is concise but lacks structure. It earns its place by being short, but conveys minimal 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?

With a moderately complex input schema (2 params, optional boolean) and an output schema present, the description fails to explain return values, side effects, or how this tool fits into the auth workflow. Incomplete for safe agent 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?

Schema description coverage is 0%, and the description adds no parameter details. It only mentions 'Cookie header' loosely, leaving both 'cookie' and 'verify' parameters unexplained.

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 the action ('Store a Cookie header') and location ('local MCP config file'), distinguishing it from sibling tools like eight_auth_login or eight_fetch_person. However, 'Cookie header' is slightly ambiguous—could be more precise like 'a cookie value'.

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?

No guidance on when to use this tool vs alternatives (e.g., eight_auth_login). The description does not mention prerequisites, context, or user scenarios.

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