get_object_storage_credentials

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that the result is meant for S3-compatible tooling, hinting the response contains usable secret material, but it does not state sensitivity (secret key exposure), permission requirements, or whether retrieval is audited — meaningful gaps for a credentials-fetching tool.

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?

Short overall and the endpoint template is front-loaded usefully, but the second sentence largely restates the first ('Get S3 compatible object storage credentials' repeated) with only the aws-cli detail as new information. Minor 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?

With no output schema, the description should hint at what a credential object contains (access key, secret key, endpoints) so the agent knows what to expect. Annotations cover safety and the schema covers inputs, but return-value shape is left unexplained.

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 four parameters are documented. The URL template [GET /v1/users/{userId}/object-storages/{objectStorageId}/credentials/{credentialId}] adds the useful detail that the three IDs form a hierarchical path, but nothing beyond that about parameter formats.

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 S3 compatible object storage credentials) and the endpoint template shows it fetches a single credential by ID, implicitly distinguishing it from list_object_storage_credentials. It does not explicitly name the sibling, but the resource and scope are 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?

The clause 'for accessing it via S3 compatible tools like `aws` cli' implies the intended purpose of retrieving credentials, which is mild usage guidance. There is no explicit when-to-use versus list_object_storage_credentials or regenerate_object_storage_credentials, and no stated prerequisites.

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