ncloud_secret_job_fail

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

With no annotations, the description carries the full burden. It discloses the caller identity and the token requirement, which is valuable, but says nothing about downstream consequences of a failure report (e.g., whether it aborts the rotation, triggers a retry, or is terminal). Adequate but incomplete for a mutation/control 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?

Two sentences, front-loaded with the action, then the calling context. No filler and no repetition of name or title.

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?

No output schema or annotations, so the description must stand alone; it covers action, caller, prerequisite token, and scope exclusion. It is nearly complete, only missing what happens to the overall rotation after a failure is reported.

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 keyIsolation fully, including the enum values. The description only restates that the job token is received by the function; it adds no format or syntax detail beyond the schema. 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 precise verb+resource ('Report a rotation job as failed') and immediately scopes it as a 'Rotation-function API (Secret Rotate Process Control)', clearly separating it from the administration siblings like ncloud_secret_execute_rotation or ncloud_secret_cancel_rotation.

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 who calls it ('the rotation trigger's function with the job token it receives') and the exclusion ('not during normal administration'). An agent knows both the correct context and when not to use it.

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