List objects in a Scaleway Object Storage bucket

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

The description adds significant behavioral information beyond the annotations: pagination mechanics (continuation token), delimiter semantics (grouping into common_prefixes and excluding matching keys from objects), and the S3 hard cap of 1000. It does not contradict 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 two sentences, front-loaded with the core purpose, and every sentence adds value. No wasted words.

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 no output schema, the description covers pagination (next_continuation_token) and delimiter behavior. It could be more explicit about the response structure (e.g., objects array, common_prefixes, is_truncated), but it is sufficient for a filtered-list tool.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by explaining the pagination flow and the effect of the delimiter, which enhances understanding beyond the schema descriptions. It does not repeat schema info.

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 verb 'list', the resource 'object keys in a bucket', and optional scoping by prefix and delimiter. It distinguishes itself from sibling tools, such as scaleway_s3_list_buckets, by specifying that it lists objects within a bucket.

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 clear context on when to use the tool (listing objects with optional prefix and delimiter) and mentions pagination. It lacks explicit exclusions or alternatives, but the context is sufficient for understanding the tool's purpose.

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