oci_os_list_buckets

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

With no annotations, the description must disclose behavioral details, but it only adds a Free Tier storage note. The claim 'List all' conflicts with the schema's limit parameter (default 100), so the tool may not return all buckets if more exist. No pagination or read-only assurance is provided.

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 sentence with a parenthetical about Free Tier limits. It is efficient and front-loaded with the action and scope, though the Free Tier note is tangential to the tool's operation.

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?

The description covers the core purpose and compartment scope, but omits behavior around the limit parameter (e.g., pagination) and return format. With no output schema, additional context about what the list contains would improve completeness. The Free Tier note is helpful context but not essential.

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 already have clear descriptions in the schema (limit and compartment_id with default to tenancy), so the description adds little beyond what the schema provides. The phrase 'in a compartment' aligns with compartment_id but doesn't enrich the meaning.

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 a specific verb ('List') and resource ('Object Storage buckets') with a clear scope ('in a compartment'), distinguishing it from sibling tools like oci_os_list_objects and oci_os_delete_bucket.

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 by stating it lists buckets in a compartment, but it does not explicitly mention when to use this tool over alternatives such as oci_os_list_objects, nor does it provide exclusions. This leaves the agent to infer appropriate usage from the resource type.

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