tool_add_cookie

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

With no annotations and a one-word description, there is no disclosure of critical behavioral traits. Does it overwrite existing cookies? Is it idempotent? What happens on failure? None of this is addressed.

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?

While extremely short, the description is under-specified rather than concise. It omits necessary details and fails to earn its place with substantive 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 complexity of an object parameter with no output schema and no annotations, the description is vastly incomplete. It does not specify cookie structure, behavior, or return values, making it nearly useless for correct invocation.

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?

The single parameter 'cookie' is an object with additionalProperties: true, meaning no structure is enforced. The description adds no meaning or constraints beyond the schema. Schema description coverage is 0%, and the description fails to compensate.

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 'Add a cookie.' is a tautology that restates the tool name without adding specificity. It does not distinguish this tool from siblings like tool_delete_cookie or tool_get_cookies, resulting in minimal purpose clarity.

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 provided on when to use this tool versus alternatives (e.g., tool_delete_cookie for removal, tool_get_cookies for retrieval). No context about prerequisites or typical use cases.

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