rabbitmq_broker_check_migration_readiness

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it verifies connections, alarms, and topology match, but does not mention side effects, authentication needs, or whether it is safe to call repeatedly. It adds useful context but leaves gaps.

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, effective sentence (13 words) that front-loads the core purpose ('Pre-flight check for blue-green migration') and then lists key verifications concisely. Every word serves a purpose.

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 (two string params, no output schema), the description covers the main checks performed. However, it does not describe the return value or format, nor does it mention prerequisites (e.g., brokers must be registered). It is adequate but could be more complete.

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%, and the description does not elaborate on the two parameters (`source_alias` and `target_alias`). Their names imply broker aliases, but no details on format, source, or constraints are provided, leaving the agent without essential semantic information.

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 as a 'pre-flight check for blue-green migration' and lists specific verifications (both brokers connected, no alarms, topology match), distinguishing it from sibling tools like `rabbitmq_broker_check_local_alarms` or `rabbitmq_broker_compare_definitions`.

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 use before a blue-green migration but does not provide explicit guidance on when not to use it or mention alternatives for non-migration checks. Usage context is clear but lacks exclusion criteria.

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