list_consumer_groups

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the output includes group IDs and state but doesn't disclose pagination behavior, potential performance cost on large clusters, or whether group state is real-time vs cached. For a read/list operation this is acceptable but could add more context.

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?

Two sentences, zero wasted words. Purpose and usage guidance are cleanly separated and front-loaded. It earns every word.

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?

An output schema exists, so return values don't need explanation. For a parameterless list tool with clear purpose and explicit usage guidance, the description is largely complete. It could add a note about volume/cost on large clusters, but the core information is present.

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 takes zero parameters and schema coverage is 100% (trivially complete). A parameterless tool needs no parameter documentation, so the baseline 4 applies. No additional param semantics are needed or missing.

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?

Clear verb+resource+scope: 'List all consumer group IDs on the cluster with their state.' It specifies the resource (consumer groups), the scope (all, on the cluster), and the output detail (state). It distinguishes itself from siblings like consumer_lag and list_topics by focusing on group IDs+state, though it doesn't explicitly name alternatives.

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?

Explicit usage guidance: 'Use this first if you don't already know a group name.' This directly tells the agent when to invoke it versus its sibling consumer_lag, which presumably takes a specific group name. This is model-worthy guidance placed right after the purpose.

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