List Cloudflare R2 buckets in your account with creation time, location, and storage class, and use a cursor to retrieve the next page.
List R2 buckets in the account with creation time, location and storage class. Pass cursor for the next page.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| cursor | No |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | No | ||
| error | No | ||
| result | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full behavioral burden. It discloses the shape of returned records and the cursor-based paging mechanism, but says nothing about permissions required, default page size behavior, or whether 'limit' caps the total result set.
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?
A single tight sentence with the core purpose front-loaded and pagination guidance appended. No filler, though the paging note is somewhat terse.
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?
An output schema exists, so return values need not be described. For a simple two-parameter list tool this is close to adequate, but the undocumented 'limit' parameter and absent behavioral details leave gaps.
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?
Schema description coverage is 0%, so the description must compensate for both parameters. It partially explains 'cursor' as the next-page token, but 'limit' (default 100) is never mentioned or defined, leaving half the parameter surface undocumented.
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?
States a specific verb and resource ('List R2 buckets') plus the account scope and the fields returned (creation time, location, storage class). It is unambiguous, though it does not need to distinguish itself from siblings, which all belong to other Cloudflare services.
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 explains the pagination flow ('Pass cursor for the next page'), which implies iterative use, but gives no explicit when-to-use guidance or prerequisites for the listing operation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.