clear_session

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

With no annotations, the description carries the behavioral disclosure burden. It states that cookies and storage are cleared, communicating the destructive nature of the operation, but it omits any details about irreversibility, required session state, or side effects on the current browsing context.

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 two short sentences that state the action and intended use with no filler. It is front-loaded and efficient.

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?

For a destructive tool with no annotations, the description is adequate but leaves gaps: it does not clarify the role of session_id, default behavior, or consequences for the current session. The presence of an output schema covers return values, but the missing parameter guidance lowers completeness.

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 description does not mention the session_id parameter or explain how it selects the session. Since schema descriptions are absent (0% coverage), the description offers no additional parameter semantics beyond the self-explanatory property name.

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 specifies the verb 'Clear' and the resource 'browser session' with details '(cookies, storage)', clearly distinguishing it from sibling tools like clear_cache or clear_history. It effectively conveys a unique purpose.

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 'Use for fresh starts' provides a clear usage context. It does not explicitly mention when not to use it or name alternatives, but the context is understandable.

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