rabbitmq_status

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

With no annotations present, the description carries the full burden of behavioral disclosure. It only states the action without describing return values, side effects, or failure modes (e.g., whether it throws if not connected). This lack of detail is a significant gap for a connection check, especially in a toolset that includes connect/disconnect operations.

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 a single, concise sentence that serves its purpose without redundancy. It front-loads the action and resource, making it easy to parse. There is no wasted information.

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?

Although the tool has zero parameters and is simple, the description is incomplete because it doesn't specify the expected output or behavior when connected vs. disconnected. Since there is no output schema, the description should explain the return value, but it doesn't. This leaves the agent unclear about what to expect from the 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?

The input schema is empty, resulting in 100% schema description coverage. Baseline is 3 because the description doesn't need to explain parameters; there are none. The description adds no parameter-level detail, but none is required.

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 states a clear action ('Check connection status') and a specific resource ('RabbitMQ broker'). It distinguishes from sibling tools like rabbitmq_connect and rabbitmq_disconnect, though it leaves ambiguity about what 'status' entails (e.g., whether it's for the current session or the broker generally).

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. For instance, it doesn't mention that this should be used before publishing to verify connectivity, or that it's a read-only operation. The absence of any contextual cues leaves the agent to infer usage from the tool name alone.

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