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 mentions 'Returns: A list of buckets' which adds some behavioral context about the output. However, it lacks details on permissions, rate limits, pagination, or error handling, which are important for a list operation with no annotations.

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 very concise with two sentences that directly state the action and return value. It's front-loaded and has zero waste, making it efficient. However, it could be slightly improved by integrating the return statement more seamlessly.

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 has 0 parameters, no annotations, and no output schema, the description is minimal but covers the basic purpose and return. It's adequate for a simple list tool but lacks depth in behavioral context and usage guidelines, making it just sufficient for minimal viability.

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, and the schema description coverage is 100%. With no parameters, the description doesn't need to add parameter semantics. The baseline for 0 parameters is 4, as it appropriately handles the lack of inputs without redundancy.

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 the tool 'List all buckets in TOS' which clearly indicates the verb (list) and resource (buckets). However, it doesn't differentiate from sibling tools like 'list_objects' which suggests it's vague about scope distinction. The purpose is understandable but lacks sibling differentiation.

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?

There is no guidance on when to use this tool versus alternatives like 'list_objects'. The description only states what it does without context or exclusions. This leaves the agent with no explicit or implied usage instructions.

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