wavexis_cookies_clear

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

Annotations already indicate destructiveHint: true and idempotentHint: true. The description adds context about using an existing session backend and the return format (JSON with status). It does not contradict annotations and provides supplementary behavioral details.

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 concise, with 4 sentences front-loaded with the main action. Every sentence adds value: purpose, alternatives, side effects, and return format, with no wasted words.

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 has a single parameter and an output schema. The description covers purpose, alternatives, side effects, and return format. It could mention that a valid session is required, but overall it is fairly complete given the simplicity of the tool.

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?

With schema description coverage at 0%, the description does not add any meaning about the session_id parameter. The schema provides a basic description ('Active session ID from wavexis_session_open'), but the description misses an opportunity to compensate, leaving the parameter's role and prerequisites unclear.

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 'Clear all cookies from the browser session' with a specific verb and resource. It distinguishes itself from siblings wavexis_cookies_delete (specific cookie) and wavexis_cookies_get (inspect), fulfilling the criteria for a score of 5.

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 explicitly provides usage context: when to clear all cookies, and when to use alternatives (wavexis_cookies_delete for a specific cookie, wavexis_cookies_get to inspect first). This offers clear guidance on when to use this tool versus alternatives.

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