get_group_members

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. However, the description adds no behavioral context beyond the basic action: it does not mention whether members are returned as a list, whether empty groups are possible, how errors are surfaced, or whether the response includes client connection metadata. This would be more critical because there is no output schema.

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, direct sentence with no unnecessary words. It is efficiently front-loaded and easy to parse, though it could convey more functional detail without becoming bloated.

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 simple two-parameter input and read-only annotations, the description is minimally viable. However, with no output schema, the description should ideally clarify what a 'member' looks like or what response shape to expect. The current description is adequate for basic invocation but leaves gaps about group membership behavior, such as empty or nonexistent groups.

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?

Schema description coverage is 100%, with both 'cluster' and 'groupName' already described in the input schema. The description adds no additional parameter-level semantics beyond what the schema already provides, which matches the baseline for full schema coverage.

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 a specific verb and resource: 'Get members of a consumer group', clearly identifying what the tool returns. It does not explicitly differentiate from sibling tools like get_group_by_name or get_group_offsets, but the resource 'members' is distinct enough to avoid major ambiguity.

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 explicit guidance on when to use this tool over alternatives. There is no mention of what other tools could be used instead, such as get_group_by_name for group metadata or get_group_offsets for offsets, leaving the agent to infer selection purely from the tool name and the terse description.

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