list-stream-consumers

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

Annotations already provide readOnlyHint: true and openWorldHint: true. The description adds no additional behavioral context beyond stating the action. It does not disclose potential edge cases, performance characteristics, or limits.

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. Information is front-loaded and efficient.

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 simple list-all tool with no parameters and good annotations, the description is mostly complete. However, it could be improved by noting the scope (cluster-wide) and suggesting filtered variants for specific cases.

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 zero parameters and schema coverage 100%, the description does not need to explain parameters. The baseline for 0 params is 4.

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 stream consumers in the RabbitMQ cluster' clearly states the verb (List), resource (stream consumers), and scope (all, cluster-wide). It distinguishes from siblings like list-consumers and list-stream-consumers-vhost by specifying 'stream' and 'all' without vhost filter.

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 implies a full list without filters but provides no explicit guidance on when to use this versus siblings like list-stream-consumers-vhost. For a tool with zero parameters, usage context is clear but alternatives are not mentioned.

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