oci_kafka_delete_cluster_config_version

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

Discloses irreversibility and required writes permission. No annotations provided, so description adds value. Could mention impact on active version if any, but adequate.

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?

Concise, front-loaded with purpose, then prerequisites and args. No unnecessary words. Excellent structure.

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?

Covers purpose, usage, parameters, and behavior. Output schema exists to handle return values. Slightly incomplete on success response, but acceptable.

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?

With 0% schema description coverage, description adds format guidance for cluster_config_id (OCID pattern) and clarifies version_number is integer. Both parameters are well-explained.

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 it deletes a specific version of an OCI Kafka cluster configuration, distinguishing it from siblings like delete_cluster_config (which deletes entire config) and delete_cluster.

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?

Provides explicit prerequisite (--allow-writes) and warns against deleting an applied version. Lacks explicit comparison to alternatives like delete_cluster_config, but context is clear.

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