rabbitmq_overview

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

The [READ] tag and readOnlyHint=true annotation jointly make clear this is a safe, non-mutating call, so the description's safety contribution is redundant rather than additive. It does not disclose auth requirements, result size/limits, or whether the broker-wide aggregation is expensive.

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?

Very tight: one summary line followed by a short args note, with the read-only marker and scope front-loaded. The bracket-tag style is terse but no sentence is wasted; the only cost is that terseness leaves room for more routing guidance.

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?

With a single optional parameter, no output schema, and readOnlyHint covering the safety profile, the description supplies what an agent needs to invoke it correctly and previews the returned categories (version, counts, rates, churn). Missing only the comparative context against sibling overview tools.

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%, so the description carries the full burden for the single 'target' parameter, and it does: it explains the parameter is a target name from config and that omitting it selects the default. That is exactly the missing semantic detail the schema lacks.

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?

States a concrete verb+resource: reading broker identity and aggregate totals (version, queue/message counts, rates, churn). It is clear what the tool returns, but it does not explicitly position itself against near-neighbors like queue_overview or list_queues, so an agent must infer the granularity difference.

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 ('overview' = broad health snapshot) and clarifies the only argument behavior ('omit for the default'), but never states when to prefer this over queue_overview, list_queues, or connection_churn_analysis. No exclusions or prerequisites are given.

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