rabbitmq_ping

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

No annotations, but the description carries behavioral weight: it explains that a low-level TCP/AMQP session and channel are established then immediately closed safely, and that a structured report is returned. Missing auth/permission details keeps it from 5.

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?

Short, front-loaded, and uses @param/@return tags efficiently. Every sentence earns its place.

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 an output schema present, the description need not explain return fields, and it already covers purpose, safety behavior, and the lone parameter. Complete for a simple ping tool.

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 coverage is 0%, so the description must compensate; it does by explaining that 'connection' is a target connection alias and defaults to 'default'. It does not add validation, format, or source-of-alias detail.

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 specific verb+resource: measuring AMQP round-trip latency to RabbitMQ, with a clear health-probe framing. It implies a distinct role from list/declare/delete siblings, even without naming one.

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?

Indicates the use case (network reachability and response-time probing), which gives clear context for when to use it. It does not name alternatives or when-not conditions, so it stops short of 5.

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