oci_kafka_disable_superuser

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

With no annotations, the description carries the full burden. It states the tool is a disable operation (mutating) and mentions the required --allow-writes flag. It does not detail reversibility or impacts, but the purpose is straightforward.

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 and well-structured: a clear purpose sentence, followed by prerequisite/usage guidance, and then a parameter definition. No redundant information.

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 low complexity (1 parameter, no annotations, but has output schema), the description covers the tool's purpose, when to use it, and the parameter meaning. It does not describe the return value, but the output schema likely does. Slightly more detail on consequences would improve completeness.

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 one parameter with no description, but the tool description adds 'cluster_id: OCI Kafka cluster OCID' in the Args section, which clarifies the parameter's meaning. However, schema coverage is 0% and the description could provide more detail like constraints or 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 'Disable the superuser for an OCI Kafka cluster' which is a specific verb-resource pair. It distinguishes from sibling tools like oci_kafka_enable_superuser and oci_kafka_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?

The description provides clear usage context: 'Use this after completing administrative tasks to restore least-privilege access' and a prerequisite ('Requires --allow-writes'). It does not explicitly state when not to use or list alternatives, but the sibling enable_superuser is the natural counterpart.

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