list_buckets

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

With no annotations provided, the description bears the full burden of disclosing behavior. It states the scope ('the user can access') but does not disclose whether the operation is read-only, any rate limits, pagination, or permission requirements. The simple 'list' verb implies a read operation, but the description adds little beyond the literal action.

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, tightly worded sentence that front-loads the action and resource. No filler or redundant information. It earns its place.

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?

Although the tool has no output schema, the description is adequate for a straightforward list operation. However, it does not mention the return format, pagination, or how the permission/provisioned filters affect results. Given the simplicity, a score of 3 reflects the clear gaps in context.

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 documents both parameters (permission and provisioned) with full descriptions, achieving 100% schema coverage. The description adds no additional meaning to these parameters beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 the specific verb 'List' with a clear resource ('storage buckets') and scope ('the user can access'), which clearly distinguishes it from sibling tools like list_clusters or list_nfs. It unambiguously states what the tool does.

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 no guidance on when to use this tool versus alternatives like list_nfs or list_lustre. It does not mention any conditions, prerequisites, or scenarios where another tool would be more appropriate. The agent is left to infer based on the resource type.

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