rabbitmq_broker_find_queues_by_threshold

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

No annotations are provided, so the description must fully cover behavioral traits. It fails to disclose whether the tool is read-only, performance implications, or result limits. The list of parameters does not convey operational behavior beyond their definitions.

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 brief, starting with a one-sentence purpose followed by a bullet-like list of parameter explanations. It is front-loaded and to the point, with no unnecessary words.

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?

Despite having an output schema (not shown), the description does not mention what the tool returns (e.g., queue names, full details). It also omits default behavior for optional parameters like vhost. For a filtering tool, more context about result structure or constraints is needed.

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?

Since schema description coverage is 0%, the description adds value by explaining each parameter's meaning (e.g., 'min_depth: minimum message count'). This clarifies the purpose of parameters that are otherwise only defined by type and default in the schema.

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 'Find queues exceeding threshold criteria,' which clearly indicates the tool filters RabbitMQ queues based on threshold parameters. It distinguishes itself from sibling tools like 'list_queues' by implying filtering, though it could be more explicit about the filtering nature.

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?

There is no guidance on when to use this tool versus alternatives like 'rabbitmq_broker_list_queues' or 'rabbitmq_broker_get_queue_info'. The description does not mention any prerequisites or scenarios, leaving the agent to infer usage context.

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