List objects in a bucket

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the '[READ]' tag merely repeats the readOnly hint. Naming the underlying ListObjectsV2 API gives an agent some known semantics, but the description never explains pagination via continuation_token or the 1000-key cap, which is the behavior an agent most needs here.

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?

Two short, front-loaded sentences with no filler, and the read marker is placed first. It is efficient, though the second sentence is largely uninformative.

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 four-parameter, paginated list tool with no output schema and no param descriptions, the definition leaves too much unsaid: no pagination contract, no prefix behavior, no return-shape hint. An agent could invoke it but not correctly handle result sets.

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% and the description explains none of the four parameters (bucket, prefix, max_keys, continuation_token). It fails to compensate for the coverage gap even though the pagination parameters carry non-obvious semantics.

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 identifies a specific verb+resource ('S3 ListObjectsV2') and the title confirms 'List objects in a bucket', so the agent knows it lists objects within a bucket. It does not differentiate from siblings like head_object or list_buckets, but the resource is unambiguous.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as head_object or get_object_text. The 'Official API Usage listObjects sample + SDK object-list' phrasing is marketing noise rather than routing guidance.

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