rabbitmq_broker_is_quorum_critical

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

The description implies a read-only check, but without annotations it does not explicitly state side effects (likely none) or define what 'minimum online quorum' means behaviorally. Minimal but not misleading.

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?

A single, front-loaded sentence that efficiently communicates the tool's function without superfluous wording.

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 absence of parameters and presence of an output schema, the description is minimally adequate but does not explain the concept of 'minimum online quorum' or how the check is performed, which could aid selection.

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?

No parameters exist, so the description trivially adds all necessary information. Baseline scores 4 when no parameters need documentation.

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 specific verb 'Check if' and resource 'quorum queues with minimum online quorum', distinguishing this health check from sibling tools like rabbitmq_broker_check_migration_readiness or rabbitmq_broker_is_in_alarm.

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 provides no guidance on when to use this check vs. sibling check tools, nor does it mention prerequisites or conditions that warrant invocation.

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