retrieve_object_storage_list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is known. The description adds the HTTP endpoint and account-scoped filtering context, but does not disclose pagination behavior, ordering defaults, or return characteristics beyond what the schema and annotations provide.

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 definition is short and front-loaded with the main action and endpoint. The second sentence repeats the listing/filtering idea from the title and first line, but the redundancy is minor and does not obscure the purpose.

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 list endpoint with eight optional parameters, rich annotations, and no output schema, the description covers the core operation but omits pagination behavior, return shape, and ordering semantics. Those gaps are partly mitigated by complete schema descriptions but leave the definition minimally adequate rather than fully complete.

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 all eight parameters are already documented in the input schema. The description adds no parameter-specific meaning or format guidance beyond the schema, making the baseline 3 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 names a specific verb and resource: list all object storages in the account, with a clear GET endpoint. It is distinguishable from the singular retrieve_object_storage by the word 'List' and 'all', though it does not explicitly name that sibling as an alternative.

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 using this tool to list and filter object storages, but it gives no explicit when-to-use guidance, prerequisites, or comparison with retrieve_object_storage. The filtering purpose is stated only briefly, leaving the agent to infer when this list operation is preferable.

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