list_objects

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It states the core action but omits details about pagination, return format (whether it returns object names, metadata, or contents), or any API-specific behavior. This is a significant gap for a tool with no output schema.

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 a single, front-loaded sentence that conveys the essential function without redundancy.

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 the simple list operation, the description is adequate but incomplete: it doesn't describe what data is returned (e.g., object names, sizes, ETags) or whether pagination is handled. The lack of an output schema and annotations makes the description the sole source of return-value information, which is insufficient.

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?

All 5 parameters have descriptions in the schema, giving high coverage. The description's mention of 'prefix filter' reinforces the prefix parameter but adds no extra semantics beyond the schema's existing documentation.

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 'Lists objects in a bucket, optionally filtered by prefix' uses a specific verb ('lists') and clear resource ('objects in a bucket'), distinguishing it from sibling tools like list_buckets which lists buckets. It clearly describes the core function.

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 implies usage for listing objects but provides no explicit guidance on when to choose this over alternatives such as list_buckets or get_bucket. No exclusions or alternative recommendations are given.

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