oci_kafka_delete_consumer_group

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

With no annotations, the description carries the full burden. It clearly warns that the operation is destructive, high risk, requires confirmation, and that the group must be empty. This provides sufficient transparency for an agent to understand the implications.

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 concise with a clear structure: purpose, warnings, prerequisites, argument, and return. It front-loads the risk information, making it efficient for quick reading.

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 tool's simplicity (single-param delete operation) and the presence of an output schema, the description covers the essentials: what it does, when to use it, and what it returns. It doesn't explain error handling, but that's acceptable for this level of complexity.

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 description for the only parameter (group_id) is 'The consumer group ID to delete,' which adds little beyond the schema's title 'Group Id.' Since schema coverage is 0%, the description is the sole source, but it lacks further detail like format or example.

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 clearly states 'Delete a consumer group,' specifying the verb and resource. It distinguishes from sibling tools like list_consumer_groups and describe_consumer_group by focusing on deletion and adding context about the destructive nature.

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?

Explicitly states prerequisites: group must have no active members (EMPTY state), requires --allow-writes, and requires confirmation. It doesn't explicitly say when not to use or mention alternatives, but the conditions are clear enough for correct usage.

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