Get object storage keys

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive, openWorld), so the lower bar applies. The description adds genuinely useful context the annotations cannot: this returns a single legacy key pair rather than all keys, and the secret is sensitive and should be handled accordingly. It does not discuss credential rotation or what happens if no key exists, which keeps it from a 5.

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 sentences: what is returned, how it differs from the sibling list tool, and a handling warning. Nothing is redundant and the core identification is front-loaded.

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 one-parameter read with no output schema, the description covers the returned value's nature (original key pair, oldest key) and its sensitivity. Minor gaps remain around the shape of the response and behavior when the unit has no key, but nothing critical for correct invocation is missing.

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 coverage is 100% and the schema description already explains that storageUnitId is the identifier obtained from list_object_storage_units. The description adds no format, encoding, or validation detail beyond the schema, so the baseline 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?

States a specific verb and resource (get the original S3 access key and secret of an object storage unit) and pins down which key it returns (the oldest one). It explicitly distinguishes itself from the sibling list_object_storage_access_keys, so an agent can choose between them without opening either schema.

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?

Gives the concrete use case (connecting S3 clients) and names the alternative with its selecting condition ('To see every key with its label, use list_object_storage_access_keys'). Both when-to-use and when-to-use-something-else are covered.

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