rabbitmq_broker_get_queue_info

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

The description lacks any behavioral details beyond the basic action. It does not disclose that this is a read-only operation, what constitutes 'detailed information', any side effects, or authorization requirements. With no annotations, the description carries the full burden, but it remains vague.

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 at 8 words, but this brevity comes at the cost of useful detail. While it is well-structured as a single sentence, it does not earn its place by providing sufficient information, making it minimally adequate.

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?

Given the lack of an output schema, the description should explain the return value or specifics of 'detailed information' to set expectations. It also fails to mention that the vhost parameter has a default value of '/'. The description is incomplete for a tool with two parameters and no output schema.

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 input schema includes two parameters (queue and vhost) with no description coverage. The tool description adds no explanation of these parameters, their values, or how to use them. Schema coverage is 0%, and the description provides no compensating clarity.

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 'Get detailed information about a specific queue' clearly states the action (get) and the target resource (queue). It distinguishes this tool from siblings like 'rabbitmq_broker_list_queues' which lists queues, and 'rabbitmq_broker_get_exchange_info' which targets exchanges.

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 is provided on when to use this tool versus alternatives. The description does not mention that this is for a single queue's detailed info, as opposed to listing queues or getting exchange info, nor does it specify prerequisites or when not to use it.

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