oci_kafka_delete_cluster_config

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

With no annotations, the description fully covers behavioral traits: it is a destructive, permanent operation that deletes all versions and affects referencing clusters. It discloses the need for confirmation and the '--allow-writes' flag.

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 well-structured with a main sentence followed by bullet-like lines. It is concise but includes all necessary warnings. Could be slightly tighter but earns its length.

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 (one parameter, destructive action) and the presence of an output schema, the description covers essential aspects: permanent deletion, version scope, and dependent resources. No return value explanation needed due to output schema.

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 input schema has only one parameter with no description (0% coverage). The description's Args section adds the OCID pattern 'ocid1.kafkaclusterconfig.*', which provides valuable context for the parameter format.

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 the verb 'Delete' and the resource 'OCI Kafka cluster configuration', with the qualifier 'permanently'. It distinguishes from siblings like delete_cluster and delete_cluster_config_version by specifying it deletes the entire config and all versions.

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 explicitly requires '--allow-writes', labels the operation 'HIGH RISK' needing confirmation, and advises updating referencing clusters before deletion. It implies when not to use (only when certain), and alternatives like delete_cluster_config_version are available among siblings.

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