describe_consumer_group

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

With no annotations present, the description carries the full burden of disclosing behavioral traits. It only states 'read', which hints at read-only access but does not confirm safety, permissions, or side effects. No information about what gets returned or any constraints is provided.

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 extremely short but lacks necessary detail, resembling a tag rather than a usable description. While conciseness is valued, this is under-specification that hinders understanding.

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 complexity of describing a consumer group in Kafka and no output schema, the description is completely inadequate. It does not mention what information is returned (e.g., offsets, members, state) or any behavioral expectations.

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?

Despite having zero parameters (schema coverage 100%), the description fails to add meaning beyond the schema. The cryptic label 'read / control_plane / DESCRIBE' does not explain what consumer group is being described or how the tool operates without any input.

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 'read / control_plane / DESCRIBE' is tautological, merely repeating the verb from the name and providing no specific information about what the tool does or what resource it acts on. It does not clarify that a consumer group is being described, nor does it differentiate from sibling tools like list_consumer_groups.

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 offers no guidance on when to use this tool versus alternatives such as describe_topic or list_consumer_groups. There is no mention of prerequisites, context, or excluded scenarios.

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