clear_session_history

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

With no annotations supplied, the description carries the full disclosure burden. It explicitly states that only command history is cleared and that working directory, environment variables, and other session state remain unaffected. It also documents the return value format, which is helpful. It could mention whether the action is reversible, but for clearing history that is likely understood.

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 and well-structured: it leads with the main action, clarifies the scope, gives the return type, and provides an example. Every sentence adds value without redundancy, and the formatting is easy to scan.

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, no-parameter tool with no annotations, the description fully covers the tool's behavior, non-effects, and return format. It is complete and self-sufficient, giving the agent all necessary information to select and invoke the tool correctly.

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?

This tool has zero parameters, so the schema is empty. The description adds context by explaining the operation but does not need to elaborate on parameters. Per the zero-parameter baseline, a score of 4 is appropriate, as the example shows the tool is called without arguments, matching 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 opens with 'Clear the session command history,' which uses a specific verb ('clear') and a clear resource ('session command history'). It unambiguously distinguishes itself from sibling tools like get_session_history and get_session_info, which handle retrieval rather than clearing.

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 provides clear context by explicitly stating what is affected and what is not, implying when to use it (when clearing history is desired). It does not name alternative tools, but the scope clarification ('Only the command history is cleared') serves as a clear exclusion of other session state.

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