list_connections

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

With no annotations, the description carries the full burden and does an excellent job. It explicitly labels the tool as '[READ]', discloses the grouping/ordering behavior, and details the return envelope including the 'truncated' flag, warning that a truncated result is not the complete set. This goes beyond what the schema provides and fully informs the agent of important behavioral traits.

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 compact and well-structured: a clear '[READ]' label, a one-sentence summary, an Args section, and a Returns section. Every sentence adds value, with no redundancy or filler.

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 tool's simplicity (one optional parameter) and the absence of an output schema, the description fully covers the tool's behavior and return format. The explicit envelope with the 'truncated' warning ensures the agent understands pagination limits, making the description complete for safe and correct invocation.

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%, but the description compensates fully by explaining the one parameter 'target' as the RabbitMQ target from config, with the default behavior when omitted. This adds meaningful semantics beyond the bare schema definition, giving the agent everything needed to use the parameter correctly.

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 lists client connections, grouped by peer host and sorted busiest first. This specific verb+resource combination distinguishes it from sibling tools like list_channels or list_queues, which focus on different RabbitMQ resources.

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 inspecting client connections, but it does not provide explicit guidance on when to choose this over alternatives like list_channels or list_queues. There are no exclusion criteria or comparative context, though the '[READ]' prefix signals it is safe for read-only inspection.

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