regenerate_object_storage_credentials

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

Annotations cover readOnly=false, idempotent=false, destructive=false, openWorld=true, but the single most important behavior is omitted: that regeneration immediately invalidates the existing secret key and breaks any client using it. The description also never says the new secret is returned in the response, and destructiveHint=false is left unqualified despite a key being unrecoverable.

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?

Two sentences where the second is a near-verbatim restatement of the first, including a typo ('for the a specific'). The endpoint path is the only incremental content; the duplication is pure waste.

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?

A mutation tool with no output schema and no annotation-based coverage of consequences. An agent cannot tell from the description that the old key stops working or what the call returns, which are the facts needed to invoke it responsibly.

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 the three required identifiers plus x-trace-id are already documented. The description adds no semantics about identifier formats or the meaning of credentialId beyond the schema baseline.

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 ('Regenerates secret key') plus the resource (S3-compatible object storage credentials) and scopes it to a user. It is distinguishable from retrieve/get/list object storage credentials siblings, though nothing explicitly names those alternatives.

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 when-to-use or when-not-to-use guidance. Nothing says whether this is for lost keys, rotation policy, compromise response, or what prerequisites (ownership, permissions) are required before calling.

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