object_storage_list_cluster_tiers

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

No annotations are present, but the description clearly signals a read-only listing operation and discloses the return content: 'List of available tiers for the cluster with pricing and limits.' It does not mention auth requirements or rate limits, but for a simple list operation this is a minor gap.

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 compact and front-loaded: the core purpose appears in the first sentence, followed by only the essential Args and Returns details. No filler or redundant information is present.

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 one-parameter list tool with an output schema, the description covers the parameter source, the purpose, and the return content. The agent has everything needed to select and invoke the tool correctly.

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 only defines cluster_id as an integer, and schema description coverage is 0%. The description compensates by explaining the parameter meaning and, more importantly, pointing to object_storage_list_clusters as the way to discover valid values. This adds operational meaning beyond the bare 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?

The description states a specific verb and resource: 'List all available tiers for a specific Object Storage cluster.' This clearly distinguishes the tool from siblings like object_storage_list_clusters by naming the exact resource (tiers) and the required scope (a specific 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 a concrete prerequisite: 'use list_clusters to see available clusters.' This tells the agent how to obtain the required cluster_id and when this tool is applicable. It does not explicitly discuss exclusions or alternative tier-listing tools, but no obvious competing tool exists.

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