chat_clearMessages

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

No annotations are provided, so the description carries the full burden of explaining behavioral traits. It merely states that messages are cleared but does not disclose whether this is irreversible, whether it affects only the local state, or if any permissions are required. This is a critical gap for a potentially destructive 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?

The description is a single, front-loaded sentence with zero wasted words. It effectively communicates the core action and target without any fluff.

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?

Despite having a well-documented schema, the description lacks essential context such as whether chatId is optional (it is not required), side effects of clearing messages, and what the return value might be. With no output schema or annotations, this leaves significant ambiguities for a destructive 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?

The input schema covers 100% of parameters with descriptions and examples, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides, making it neutral in this dimension.

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 clearly states the action 'Clear' and the target 'all messages from the chat', making the primary purpose evident. However, it does not differentiate from similar sibling tools like chat_delete or chat_clearState, so it falls short of full distinctiveness.

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 intended use is implied: use this tool when you want to clear all messages in a chat. However, there is no explicit guidance on when not to use it nor any mention of alternatives, such as chat_clearState or chat_delete.

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