List S3 objects

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so the safety profile is covered. The description adds a valuable limitation (metadata not returned) but says nothing about pagination behavior despite exposing a continuationToken, so added behavioral context is partial.

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?

Three short, front-loaded sentences with zero filler; purpose first, then the browsing idiom, then the sibling-routing caveat.

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?

Adequate for a read-only list tool whose annotations carry safety, but for a paginated list with a continuationToken parameter and no output schema, an agent gets no description of what the response contains or how to page. This is a meaningful gap for correct invocation.

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 100%, so parameters are already fully documented. The description's mention of prefix/delimiter semantics and the metadata note adds marginal value but no syntax or format detail beyond the schema; baseline 3 applies.

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 objects in a bucket') and names the sibling it is not (s3_head_object), with scope clarified by prefix/delimiter for folder-style browsing. An agent can distinguish this from s3_list_buckets and neighboring object tools without opening schemas.

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?

Explicitly routes metadata lookups to s3_head_object and implies folder-style browsing via prefix/delimiter. It does not, however, cover when-not-to-use beyond the metadata case, e.g. no guidance on choosing this over s3_list_buckets or on pagination workflows.

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