set_cookies

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that cookies are injected and gives a Burp export example; it does not disclose whether existing cookies are overwritten, whether the operation persists, what permissions are needed, or what the result will be.

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 that immediately conveys the tool's purpose and a common use case. There is no wasted text or redundant restatement of the schema.

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?

Despite having only one parameter and no output schema, the tool lacks annotations and the cookie item schema is empty. The description does not adequately explain cookie object structure or behavioral effects, leaving important gaps for an agent trying to invoke it correctly.

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 schema shows only 'cookies' as an array of bare objects, with 0% description coverage. The description provides a 'Burp export' hint but does not explain the required fields or shape of each cookie object, leaving the agent to guess what properties such as name, value, domain, or path are expected.

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 specifies the action ('Bulk-inject') and the resource ('cookies'), and the 'Bulk' qualifier distinguishes this from the sibling set_cookie tool. The example 'from Burp export' also anchors the intended use as importing multiple cookies at once.

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 phrase 'Bulk-inject cookies' plus the Burp export example provides clear context for when this tool is appropriate. It implies use when you have multiple cookies to set, but it does not explicitly name set_cookie as the alternative for single-cookie scenarios.

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