scratchpad_clear

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

With no annotations provided, the description must disclose behavioral traits. It does not mention that clearing is irreversible, whether any confirmation is required, or what happens to the data. As a destructive operation, this lack of safety information is a significant gap.

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?

Two short sentences: the first states the action, the second gives the usage context. No filler words, clearly front-loaded, and every sentence earns its place.

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 is simple with one optional parameter and no output schema, so the description is mostly adequate. However, for a destructive clear operation, it should disclose irreversibility or side effects; without this, the description leaves a gap in the agent's ability to anticipate consequences.

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 already fully describes the session_id parameter ('Only clear this session key; omit to clear all'). The description adds no new meaning beyond restating this, so it provides no additional value over the schema.

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 explicitly states the action ('Clear scratchpad working notes') and scope ('one session key, or everything'), using a specific verb and resource that clearly distinguishes it from sibling tools like scratchpad_read and scratchpad_write.

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?

It provides clear context ('Use when a task completes and its intermediate state is no longer needed') that tells when to invoke the tool. However, it does not explicitly name alternative tools or state when not to use it, though the context strongly implies a cleanup role.

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