cloud_storage_list_buckets

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

No annotations are provided, so the description carries the full burden. It discloses the return format (list of dictionaries with name and region fields), which is valuable behavioral information. However, it does not mention potential limitations like rate limits, authentication requirements, pagination behavior, or error conditions, leaving gaps in operational transparency.

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 extremely concise and well-structured: the first sentence states the purpose, and the second clearly documents the return format. Every sentence adds essential value with zero wasted words, making it easy for an agent to parse and understand.

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 tool's simplicity (0 parameters, no output schema, no annotations), the description is nearly complete: it explains what the tool does and what it returns. However, it lacks information about behavioral aspects like error handling or performance characteristics, which would be helpful for robust agent operation.

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 tool has 0 parameters with 100% schema description coverage (empty schema). The description does not need to explain any parameters, which is appropriate. No additional parameter semantics are required, so it meets the baseline for this condition.

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 clearly states the specific action ('List all buckets') and resource ('across all regions'), distinguishing it from siblings like 'cloud_storage_list_objects' (which lists objects within a bucket) and 'cloud_storage_get_bucket_location' (which gets location for a specific bucket). The verb 'List' is precise and the scope 'across all regions' is explicitly defined.

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 needing to enumerate all storage buckets globally, but does not explicitly state when to use this tool versus alternatives like 'cloud_storage_list_objects' or 'cloud_storage_get_bucket_location'. No exclusions or prerequisites are mentioned, leaving the agent to infer context from the tool name and description alone.

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