neuron_delete_cookie

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

No annotations are provided, so the description carries the full burden. It discloses that the operation deletes, but does not state what happens if the cookie does not exist, whether deletion applies to all paths or a single path, whether it is immediate or reversible, or what the return value is. The 'URL context' wording is vague about how strictly the URL must match.

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?

A single nine-word sentence that is front-loaded with the action verb and contains zero filler. It earns its place entirely.

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?

The tool is simple (two string parameters, no output schema), and parameter semantics are fully covered by the schema. However, because this is a destructive operation with no annotations, the description should ideally clarify failure behavior and the precise scope of deletion (URL matching, path), which are currently absent.

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 100%, so both 'url' and 'name' are already documented in the schema. The description's 'by name and URL' phrase merely mirrors the schema rather than adding deeper meaning about URL matching semantics or cookie scope.

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 ('Delete') and a precise resource ('a specific cookie by name and URL'), making the core action unambiguous. It is clear but does not explicitly differentiate from nearby siblings like neuron_set_cookie, neuron_get_cookies, or neuron_clear_storage.

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?

There is no guidance on when to use this tool versus alternatives, no exclusions, and no mention of sibling tools such as neuron_clear_storage for bulk deletion or neuron_set_cookie for modification. Usage context is left entirely to inference from the name.

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