neuron_set_cookie

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

With no annotations, the description must carry the full behavioral burden, but it only states the high-level action. It does not disclose overwrite semantics, permission requirements, session effects, or error handling, which are important for a mutating cookie operation.

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 short and free of fluff, but it is under-specified for a tool with 9 parameters. This is not effective conciseness; it borders on missing critical 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 no output schema, no annotations, and 9 parameters with 3 required, a single generic sentence is grossly inadequate. The agent has no information about defaults, constraints, side effects, or return behavior.

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 only 33%, and the description adds no parameter-level meaning. It fails to explain name, value, domain, secure, httpOnly, sameSite, or expirationDate, leaving the agent with no additional semantic help beyond the bare 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 states a specific verb ('set') and resource ('cookie'), which clearly conveys the tool's purpose. It is distinguishable from sibling tools like neuron_get_cookies and neuron_delete_cookie by action, though the phrase 'on a domain' is slightly imprecise since cookies are set on a URL and domain is optional.

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 explicit guidance on when to use this tool versus alternatives. It does not mention creating vs. updating cookies, nor does it contrast with get/delete cookie tools, leaving the agent to infer usage entirely from the tool's name.

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