echopath_clear_history

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

With no annotations, the description carries the full behavioral burden. It does disclose the two things destroyed (in-memory sessions and local history artifacts), but never states that the operation is destructive/irreversible, whether it is global or scoped, or that the confirm flag gates execution.

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?

A single front-loaded sentence with no filler or repetition. It is efficiently sized, though the brevity comes at the cost of the missing behavioral detail noted elsewhere rather than from deliberate pruning of low-value content.

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?

An output schema exists, so return values need not be explained, but a destructive zero-annotation tool should clarify scope, irreversibility, and the role of confirm. None of that is present, leaving the agent under-informed before an irreversible action.

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 description coverage is 0% and the single parameter 'confirm' (boolean, default false) is never mentioned in the description. For a destructive tool, the meaning and gating behavior of confirm is exactly the kind of detail the description should supply, and it is absent.

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 pairs a clear verb ('Clear') with specific resources ('in-memory sessions and local EchoPath history artifacts'), and the EchoPath scoping separates it from generic session tools. It does not explicitly name a sibling to contrast against (e.g., echopath_list_sessions), but the destructive clearing action is unmistakable.

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?

There is no statement of when to use this versus the many session/history siblings (list_sessions, get_session, create_session), nor any preconditions or warnings. The agent must infer that this is a cleanup/reset operation from the verb alone.

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