ncloud_secret_job_generate_random_secret

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

Annotations are empty, so the description carries the full burden. It discloses the non-obvious behavioral traits: this is an internal rotation-process API, requires the injected job token, and returns the secret value in plain text (flagged with a warning). It does not cover auth scope beyond the token, rate limits, or whether the generated value is persisted, keeping 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, front-loaded sentences: purpose, calling context, and a high-value warning. No filler, and the security-relevant plaintext warning is given prominence with a ⚠️ marker.

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 11 parameters, no annotations, and no output schema, the description adequately covers purpose, invocation context, and the sensitive nature of the response. The schema covers parameter semantics fully, so the remaining gap is minor: no detail on the returned value's format or lifetime.

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% and documents all 11 parameters including ranges, defaults, and the keyIsolation host semantics, so the schema does the heavy lifting. The description adds no parameter-level detail (e.g., constraints on length or how exclusion flags interact), leaving this at the baseline 3.

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+resource (generate a random secret string) and scopes it to a rotation job, distinguishing it from the sibling ncloud_secret_job_* lifecycle tools and from administration-time secret tools. An agent can identify exactly what this tool produces without opening the 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?

Explicitly states the calling context (rotation trigger's function using its job token) and an exclusion ('not during normal administration'), which is strong when-to-use guidance. It stops short of naming the alternative tool an administrator should use instead, so it falls just short of a 5.

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