oci_kafka_enable_superuser

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

With no annotations, description discloses superuser access, the optional duration parameter, and that without a duration it stays enabled until explicitly disabled, plus a warning for careful use.

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?

Four concise sentences: action, prerequisite, warning, and parameter descriptions. No redundancy, front-loaded with core purpose.

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, parameters, and key behavioral aspects (duration behavior, need for --allow-writes). With no output schema needed (the description doesn't require return info), it's nearly complete.

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?

Both parameters are described with their purpose and behavior beyond schema titles; the duration parameter's default and effect are explained, adding value beyond 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?

Clearly states it enables superuser for an OCI Kafka cluster, distinguishes from the sibling 'oci_kafka_disable_superuser' by specifying enablement and notes the superuser's full administrative access.

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?

Specifies a prerequisite ('Requires --allow-writes') and advises sparing use with a time limit, but does not explicitly list when not to use or mention alternative tools beyond the implied complement disable.

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