clear_stored_data

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

The description discloses that the tool deletes from disk and memory, implying a destructive operation. With no annotations, it provides basic behavioral context but does not cover irreversibility or error handling. It is adequate but not extensive.

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 sentences long with no fluff. It front-loads the action and immediately clarifies the parameter usage, making it highly 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 simple deletion tool with one parameter, the description is complete. It covers both usage modes. The presence of an output schema means return values are handled elsewhere. It could mention confirmation or side effects, but it is sufficient.

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 description's parameter explanation ('Pass a specific data_id to remove one item, or omit to clear all') is nearly identical to the schema's description. It adds minimal new 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 uses a specific verb 'Delete' and clearly identifies the resource as 'stored signals and spectra'. It distinguishes this tool from sibling tools like list_stored_data (read) and load_signal_from_file (load).

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 states when to use each variant: pass a specific data_id to remove one item, or omit to clear all. It does not mention exclusions or alternatives, but the instructions are clear and actionable.

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