coeus_clear_conversation

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

There are no annotations to indicate destructive or side-effect behavior, so the description carries the full burden. It does add one useful trait — the session is in-memory, implying ephemerality — but it does not disclose whether the action is irreversible, whether it affects persisted conversation data, or what happens to the session after being cleared.

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 one short, focused sentence with no filler or repetition. It front-loads the action and resource immediately and every word contributes to understanding.

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 only one parameter and a simple schema, the tool performs a potentially destructive action with no annotations and no output schema. The description does not explain expected return behavior, side effects, or usage context, leaving an agent to guess important aspects of invoking it 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?

The input schema already documents conversation_id with 100% coverage, so the baseline is 3. The description adds no additional meaning about where the ID comes from, what format it should have, or how to obtain it, but it does nothing to make the parameter harder to understand.

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 uses a clear verb ('Clear and a specific resource ('an in-memory conversation session'), and it is easily distinguished from conversation-related siblings like start_conversation, continue_conversation, and list_conversations. It could be slightly more explicit about whether this deletes the session record or simply resets its context, but the core purpose is understandable.

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?

No guidance is given about when this tool should be used instead of start_conversation, continue_conversation, or list_conversations. Usage context is only implied by the operation name, so an agent receives no explicit selection criteria.

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