oci_adb_start

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Start a stopped Autonomous Database' without mentioning side effects, async behavior, permission requirements, or what happens if the database is not stopped. This leaves the agent without critical behavioral context.

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 a single, concise sentence: 'Start a stopped Autonomous Database'. It is front-loaded with the action and resource, contains no fluff, and every word earns its place.

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 lack of annotations, no output schema, and only one parameter, the description is minimal. It does not mention prerequisites (e.g., the database must be stopped), expected outcomes, or return values, which are important for a state-changing operation. This leaves the description incomplete for an agent to fully understand the tool's behavior.

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 schema has 100% coverage for the single parameter database_id, described as 'Autonomous Database OCID'. The description adds no parameter-specific meaning, so the baseline score of 3 applies because the schema already fully documents the parameter.

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 uses the specific verb 'start' with the resource 'Autonomous Database', clearly indicating the tool's function. This distinguishes it from siblings like oci_adb_stop and oci_adb_get, which share the same resource but different actions.

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 implies usage—when a stopped Autonomous Database needs to be started—but does not explicitly state when to use it versus alternatives such as oci_adb_stop, nor does it mention prerequisites or constraints. This is implied usage rather than explicit guidance.

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