rabbitmq_bind_queue

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

No annotations are provided, so the description carries the full burden, and it does disclose one meaningful behavioral trait: the operation is gated by the global write-protection flag (--allow-write). It does not state idempotency (what happens if the binding already exists), required permissions, or whether the operation is reversible — significant gaps for an unannotated mutation tool.

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 purpose sentence is front-loaded and the @param list is efficiently formatted, with no padding. The param block is justified given the 0% schema coverage, though the header ordering of the write-gate note before the params is slightly awkward.

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?

An output schema exists, so the description needn't detail return values and only points at the binding report, which is fine. Combined with full parameter documentation and the disclosed write gate, it covers what an agent needs for this mutation tool, though it could say more about failure/idempotency behavior given the absence of annotations.

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%, so the description must compensate, and it does: it documents all five parameters with meaning and defaults (routing_key defaults to empty, connection defaults to 'default', arguments is optional). The only shortfall is that 'arguments' is left as a vague 'optional binding arguments' with no hint about its expected shape.

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: binding a queue to a named exchange with a routing key. The verb 'bind' clearly separates it from siblings like rabbitmq_unbind_queue and rabbitmq_list_bindings. It does not, however, explicitly name those alternatives, so it stops short of full sibling differentiation.

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?

Usage is implied by the clear 'bind' verb and the mention of the global write gate, which tells the agent this is a write operation. But there is no explicit when-to-use/when-not guidance and no reference to unbind_queue or list_bindings as alternative choices.

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