list-consumers-vhost

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

The description claims 'List all consumers' but the annotation openWorldHint: true indicates the list may not be complete, creating a contradiction. No additional behavioral traits (e.g., pagination, auth needs) are disclosed beyond annotations.

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 wasted words. However, it could include more detail without becoming verbose, such as mentioning the tool returns consumer details.

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 low complexity (1 param, no output schema, annotations present), the description tells what the tool does and the key parameter, but omits what consumer information is returned (e.g., channel, queue, tag). Adequate but incomplete.

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?

With 0% schema description coverage, the description only adds 'for a specific vhost' to clarify the vhost parameter's role. This provides minimal additional meaning over the schema's type and required flag.

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 'List all consumers for a specific vhost' clearly identifies the verb (list), resource (consumers), and scope (specific vhost), distinguishing it from siblings like list-consumers (no vhost filter) and list-consumers-queue (by queue).

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 alternatives (e.g., list-consumers-queue for queue-specific consumers). No when-not-to-use or context hints are given.

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