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. It mentions 'bypass login' which hints at a side effect of authentication bypass, but does not detail other behavioral aspects like whether it modifies server-side state, if it requires prior session, or what happens to existing cookies.

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 consists of only two sentences, both essential and to the point. No wasted words, and the key information is front-loaded.

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?

While the description explains the purpose and use case, it lacks detail on what the tool returns (no output schema) or how to verify success. It also does not mention if cookies persist across sessions or if there are any prerequisites. Given the tool's potential impact, more context would be beneficial.

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 coverage is 100% and the parameter descriptions in the schema are already detailed, especially for cookies (name, value, domain, path). The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 states the action ('Set session cookies') and the resource ('for a project'). It also explains the use case ('bypass login with existing session'), which distinguishes it from sibling tools like get_cookies (read) and login_project (interactive).

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 clear guidance on when to use this tool ('bypass login with existing session'). However, it does not explicitly mention when not to use it or alternatives, though the context implies its specific purpose.

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