list_r2_catalogs

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

No annotations are provided, so the description carries the transparency burden. It conveys a read-only listing action and the account scope, which is useful, but it does not disclose pagination, result shape, ordering, or other API behavior relevant to a list operation.

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?

One short, front-loaded sentence with no filler or repetition. Every word carries meaning and the structure is maximally easy to parse.

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 account-scoped list operation, the core invotation is clear and the schema supplies the required parameter. However, the absence of an output schema and any mention of pagination or return format leaves some context incomplete.

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 only parameter, account_id, is already fully described by the input schema (100% coverage). The description's 'for an account' merely echoes the schema and adds no additional semantic detail about the parameter.

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 ('List'), a specific resource ('R2 catalogs'), and an account scope. The plural form and resource name clearly distinguish it from siblings like get_r2_catalog (singular fetch) and list_r2_buckets (different R2 resource).

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 encodes the use case: call this when enumerating R2 catalogs for an account. It does not explicitly name alternatives or state when not to use it, so some inference is required from the sibling list.

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