clear_chat_history

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

With no annotations provided, the description carries full burden. It discloses the destructive nature (delete), scope (local only), and return value (confirmation or not-found). Additional details like authentication or side effects are not needed for this simple operation.

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?

Extremely concise: one sentence for purpose, then a brief note on scope, followed by Args and Returns sections. Every sentence adds necessary information with no redundancy. Front-loaded with the key action.

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?

Given low complexity (1 parameter, no output schema, no nested objects), the description is complete. It explains what the tool does, the parameter, the return value, and the behavioral scope (local vs server). No missing information for effective use.

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 0%, but description fully compensates: 'Session name whose chats/{session}.json file should be deleted' explains the parameter's meaning and usage (forms the filename). Adds value beyond the schema definition.

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?

Clearly states 'Delete the local history file for a chat session', specifying the action (delete), resource (local history file), and scope (chat session). Distinguishes from sibling tools like 'delete_file' (generic) and 'delete_stateful_response' by focusing on chat history locally.

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?

Provides clear context by stating it only removes the client-side JSON file and leaves server-side responses untouched, implying when to use this tool (local-only deletion) and when to look elsewhere (server-side). Does not explicitly name alternative tools but offers sufficient situational guidance.

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