list_consumers

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

There are no annotations, so the description carries the behavioral burden. It does disclose that only "active" consumers are listed and that the result includes queue assignments, prefetch, and connection info, which is useful. However, it does not explain the default vhost scope, whether inactive consumers are always omitted, or any permission/visibility constraints.

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 focused sentence that front-loads the action and resource, then lists the returned fields. There is no redundancy or unnecessary detail.

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?

This is a simple tool with one optional parameter, and the description provides enough about what is returned to make the call understandable. With no annotations and no output schema, a bit more about default vhost behavior or ordering would help, but for a straightforward read-only list operation the gap is minor.

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 only parameter, vhost, is fully documented in the schema as "Filter by vhost" (100% schema coverage). The description adds no additional parameter semantics beyond this, so the baseline 3 is appropriate.

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 uses the specific verb "List" and names the resource (consumers) plus the included fields (queue assignments, prefetch, connection info). This clearly distinguishes it from sibling tools like list_connections and list_queues even without opening their schemas.

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?

No guidance is given on when to use this tool versus alternatives, and no exclusions or prerequisites are stated. The name implies listing consumers, but the description does not say why an agent should choose it over list_connections for connection-level details or list_queues for queue-level details.

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