event_bus_bus_clear

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

No annotations are provided, so the description is the sole source for behavioral context. It states what is cleared (history and subscribers) but does not disclose that this is a destructive, irreversible operation or any permission requirements. The transparency is minimal but not misleading.

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 very concise, one sentence with minimal waste. It front-loads the context '[event_bus]' and immediately conveys the core function. It could be slightly more structured but is effective.

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?

For a simple tool with one optional parameter and an output schema, the description covers the basic purpose. However, it lacks details about return value, error conditions, or safety warnings. Given the absence of annotations, more context would be helpful for safe usage.

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 description explains that omitting the 'topic' parameter clears all topics, and includes the topic name parameter. However, it does not clarify what constitutes a valid topic name or any constraints. Since schema coverage is 0%, the description adds some value but could go further.

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 resource (history and subscribers for a topic, or all topics). It distinguishes from siblings like bus_publish, bus_subscribe, etc., as the only clear operation on the event bus.

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 on when to use this tool versus alternatives (e.g., viewing history with bus_history or managing subscriptions individually). There is no mention of prerequisites, side effects, or recommended use cases.

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