kafka_reset_consumer_group_offsets

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

With no annotations, the description carries the full burden, and it does meaningfully disclose the destructive/high-risk nature and the dry-run safety mechanism — the most important behavioral facts for this tool. It stops short of explaining the confirm/force interplay or what a non-dry-run call irreversibly changes.

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?

A single dense sentence, front-loaded with purpose followed by risk and capability notes. No wasted text, though the parenthetical packs several ideas together.

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 need no explanation, and the description covers purpose, risk and strategy options. But for a complex 10-param destructive tool with no annotations, the confirmation semantics (confirm/force) and required-param expectations are missing.

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 0% across 10 params, so the description must compensate. It only names the strategy values (earliest/latest/to_offset/to_datetime, which the schema lacks) and dry-run; 8 params such as offset, confirm, force, partitions and datetime_val remain unexplained anywhere.

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 states a specific verb+resource+scope: reset a given consumer group's offsets on a target topic. No sibling tool (list/describe/produce/create/delete) performs offset reset, so the purpose is unambiguous and easily distinguished.

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?

It flags this as a high-risk operations action and notes Dry-Run pre-check support, implying 'use carefully / run dry-run first', but gives no explicit when-to-use vs when-not guidance or prerequisites beyond that. Usage is inferable rather than stated.

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