rabbitmq_overview

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

Although no annotations are provided, the description explicitly marks the operation as [READ], indicating it's a safe, non-mutating call. It also discloses the kind of information returned. However, it doesn't detail any potential limitations or required permissions.

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 extremely concise, with a clear one-line summary and a minimal args block. Every sentence adds value.

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 read-only overview tool with one optional parameter and no output schema, the description adequately covers the tool's purpose, the parameter, and the type of data returned. It is complete for the tool's complexity.

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 'target' is a RabbitMQ target name from config and can be omitted for the default, adding meaning beyond the schema's type/default. This is sufficient for the single parameter.

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 identifies this as a read-only broker overview tool, listing specific data (version, queue/message counts, rates, churn). The [READ] tag and 'Broker identity + totals' distinguish it from sibling tools like queue_overview or list_queues.

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 a high-level broker summary but does not explicitly state when to use this tool versus alternatives. It doesn't provide exclusion criteria or compare to sibling tools.

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