object_storage_list_objects

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

With no annotations, the description carries the burden of behavioral disclosure. It explains the 1000-object limit and pagination via 'is_truncated' and 'continuation_token', adding value. However, it does not explicitly state that the operation is read-only or discuss authorization needs.

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 concise sentences with the purpose stated first. Every sentence adds value: purpose, pagination limit, continuation token usage. No fluff.

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?

The description covers the critical pagination behavior. Since an output schema exists, it need not detail return values. It lacks mention of sorting or output fields like object keys/metadata, but is adequate for a list operation.

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 each parameter is already documented. The tool description adds no extra meaning beyond the schema; it focuses on output behavior (pagination), not parameter details. Baseline score of 3 is appropriate.

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 'List objects in a bucket (one page)', using a specific verb and resource. It also mentions pagination, distinguishing it from sibling tools like object_storage_list_buckets or object_storage_get_object_metadata.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., listing buckets vs. objects). The description only covers pagination mechanics but does not mention when not to use or suggest other tools.

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