rabbitmq_broker_get_connection_churn

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It implies a read-only operation ('get') but does not clarify whether it aggregates data across all connections or by broker, nor does it mention any performance implications or data freshness. The minimal description leaves critical behavioral traits unsaid.

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 with no unnecessary words. It is appropriately front-loaded. Given the tool's simplicity, this level of conciseness is ideal.

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?

For a tool with no parameters and no output schema, the description is minimally adequate. However, it does not explain what 'churn rates' represent (e.g., connections per second, total counts) or how the result can be interpreted. This lack of detail leaves the agent potentially uncertain about the output format.

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 tool has zero parameters, and the input schema is empty, so 100% schema coverage is trivial. Per the guidelines, a baseline of 4 is appropriate for 0-parameter tools. The description does not add parameter-specific meaning, but none is needed.

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 'Connection and channel churn rates' clearly identifies the tool's purpose of retrieving churn metrics for connections and channels. It specifies the resource (connection/channel churn rates) but does not elaborate on what 'churn' means (e.g., rate of new vs closed connections), which slightly reduces clarity.

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 tool versus sibling tools like rabbitmq_broker_get_overview or rabbitmq_broker_list_connections. It does not explain the context in which churn rates are relevant or how they differ from other monitoring tools.

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