kafka_delete_topic

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

With no annotations, the description carries the full burden and does disclose the critical trait: this is a destructive, high-risk operation that requires explicit confirm=True. It stops short of stating irreversibility, required permissions, or the effect on active consumers/producers.

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 front-loaded sentence carrying the action, the risk level, and the confirmation requirement with zero filler. Nothing to trim.

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. The description covers the destructive nature and the confirm gate, but omits permissions/auth requirements and irreversibility, which matter for a destructive operation with no annotations.

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 coverage is 0%, so the description must compensate. It fully explains the non-obvious `confirm` parameter (must be explicitly True), which is the semantically important one; `topic_name` is self-evident from its name. It adds real meaning beyond the bare boolean/default in the schema.

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?

States a specific verb and resource ('delete topic from Kafka cluster'), which is unambiguous and inherently distinct from all siblings (list/describe/create/produce). An agent immediately knows what this tool does without opening the schema.

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 flags the operation as high-risk and states the confirm=True prerequisite, which is useful gating guidance. However, it never says when to use this versus alternatives (e.g. kafka_describe_topic to verify before deleting) or when not to use it, so usage routing is only implied.

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