bus_reset

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions archiving and starting a new conversation but omits side effects like irreversibility, permission requirements, or what exactly happens to existing messages and users. The term 'archive' is ambiguous.

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, compact sentence of seven words, directly and front-loaded with the verbs 'Archive' and 'begin'. Every word contributes meaning, with no filler or redundancy.

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 the simple zero-parameter design, the description leaves critical context unresolved: it does not clarify whether 'archive the active room' means removing the room or just clearing the conversation, nor does it indicate what the agent should expect as a result. Without an output schema or annotations, this ambiguity makes the description incomplete for a mutation tool.

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 tool has zero parameters, so schema coverage is trivially complete. The description does not need to explain parameter behavior, and it does not attempt to add unnecessary detail, making this a solid baseline.

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 ('Archive the active room and begin a new conversation') and identifies the resource (active room). This distinguishes it from sibling tools such as bus_open, bus_close, bus_send, and bus_read, which perform different operations.

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?

There is no explicit guidance on when to use bus_reset versus alternatives, nor any mention of prerequisites, exclusions, or scenarios where a different tool would be more appropriate. The intended use case is implied but not stated.

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