event_bus_bus_stats

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

No annotations are provided, so the description carries the full burden. It indicates a read-only behavior by returning data, but does not explicitly state whether it has side effects, requires authentication, or if the statistics are cumulative or reset. The description adds some context but lacks thorough behavioral details.

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 sentence with a prefix [event_bus] for organization. It is front-loaded with the prefix and then concisely states the output. No unnecessary words.

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?

The description covers the main output: total events and per-subscriber counts. Since an output schema exists, it doesn't need to detail return values. It could mention whether the stats are since last reset or lifetime, but the information provided is sufficient for a simple stats 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?

There are zero parameters, and the schema coverage is 100%. The description does not add parameter semantics since there are none to describe. Baseline 3 is appropriate, and the description's mention of output details (events published, per-subscriber counts) is not about parameters.

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 tool returns 'total events published and per-subscriber call counts', which is a specific verb+resource. It distinguishes from sibling tools like event_bus_bus_publish, event_bus_bus_subscribe, etc., by focusing on statistics instead of actions.

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 usage for getting bus stats, but does not provide explicit guidance on when to use this tool versus alternatives like event_bus_bus_history or event_bus_bus_subscribers. No when-to-use or when-not-to-use context is given.

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