rabbitmq_overview

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

With no annotations, the description carries the full burden, but it does disclose a genuine behavioral trait: graceful degradation when the Management API is absent, plus the ADR-0001 dual-core architecture context. It does not clarify read-only safety, permissions, or whether the fallback yields partial data, so it is useful but incomplete.

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 purpose is front-loaded in the first line, followed by the degradation caveat and param/return tags. Reasonably tight, though the ADR-0001 architecture reference is internal jargon that adds little for an invoking agent.

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?

An output schema exists, so return values need not be explained, and the single optional parameter is covered. What is missing is usage context — when to call this instead of the many granular rabbitmq_* siblings — leaving the agent to infer the routing.

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?

Schema description coverage is 0% for the single 'connection' parameter, but the description compensates by defining it as the target connection alias with a 'default' value. That explains the parameter's meaning; the default itself is already in the schema, so the added value is modest.

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 states a specific resource and scope ('cluster node status, queue statistics, and global message throughput dashboard'), which clearly separates it from the list/get siblings like rabbitmq_list_queues or rabbitmq_get_queue. It doesn't explicitly name those siblings, but the cluster-wide aggregation framing is distinct enough for an agent to route correctly.

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 guidance on when to prefer this overview over the granular sibling tools, nor any prerequisites. The only conditional statement ('automatically degrades when Management API is not configured') is a runtime behavior, not a usage recommendation.

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