oci_adb_get

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only states the purpose and does not mention whether the operation is read-only, what specific information is returned, or any potential side effects or prerequisites. While 'get' suggests a read, the description lacks explicit 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 with no extraneous content. It is front-loaded with the verb 'Get' and the resource, making it immediately scannable.

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?

For a simple get operation with one parameter and no output schema, the description is minimal but adequate. However, 'detailed information' is vague and does not hint at the return structure or fields. Given the lack of annotations and output schema, a bit more context about what details are included 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?

Schema description coverage is 100% with database_id described as 'Autonomous Database OCID'. The tool description adds no additional meaning beyond the schema, so the baseline of 3 applies. It does not clarify format, required format, or how to obtain the OCID.

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 'Get detailed information about an Autonomous Database' clearly specifies the verb (get), resource (Autonomous Database), and level of detail. It distinguishes itself from sibling tools like oci_adb_list, which presumably lists databases, and oci_adb_start/stop, which perform 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 does not explicitly state when to use this tool versus alternatives. However, the phrasing 'Get detailed information' implies usage when detailed information about a specific database is needed, contrasting with list operations. No exclusions or alternative recommendations are provided.

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