ncloud_secret_job_start

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

Annotations already establish idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: it is a control-plane call made by the rotation function itself, using the injected job token, which explains its behavioral role in the rotation lifecycle.

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 short sentences, front-loaded with the core action and followed by the scoping constraint. No filler; every clause earns its place.

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?

Given a 3-parameter tool with full schema coverage, no output schema, and covering annotations, the description supplies the essential lifecycle and caller context an agent needs. It does not describe return values, but with no output schema that is not required.

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 schema already documents secretId, jobToken, and the keyIsolation enum in detail. The description reinforces that the token is one the function "receives," but adds little parameter meaning beyond the structured fields. Baseline 3 applies.

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 ("Report the start of a rotation job") and situates it within the "Rotation-function API" so it is distinguishable from sibling job tools like ncloud_secret_job_complete or ncloud_secret_job_fail. It does not explicitly name a sibling, but the scope is 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?

Explicitly states both when and when-not to use it: it is "meant to be called by the rotation trigger's function with the job token it receives, not during normal administration." This is a clear usage boundary that routes an agent away from calling it in ordinary admin flows.

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