semantic_clear

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

The description explicitly warns 'This action is irreversible,' disclosing a critical destructive trait. Since no annotations are provided, this disclosure carries the full behavioral burden, and while it doesn't detail all potential side effects, it covers the most important safety aspect.

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 consists of two short sentences: the action and a warning. Every word earns its place, with no redundant details or filler.

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 the tool's simplicity (one parameter, no output schema), the description conveys the core operation and its irreversibility clearly. It doesn't describe return values or error handling, but for a destructive clear operation, this level of detail is generally 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?

The schema already provides a complete description for the sole parameter 'collection' (100% coverage). The tool description adds no parameter-specific meaning beyond what the schema states, so it provides no bonus over the structured data.

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'), the object ('all indexed documents'), and the scope ('from a collection'), making it distinct from sibling tools like semantic_index and semantic_search. The purpose is unambiguous and specific.

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 implies the tool is used to permanently remove all indexed documents from a collection, but it does not explicitly state when to use it versus alternatives, nor does it mention any prerequisites or exclusions. Usage context is implied rather than explicitly guided.

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