ncloud_functions_get_action_activation_detail

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

Beyond the readOnlyHint annotation, the description discloses the return payload structure and, more valuably, an eventual-consistency behavior with a specific error code and a retry recommendation. This is exactly the kind of behavioral context agents need to handle transient failures gracefully.

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 carry high information density with no filler. The core purpose and return fields are front-loaded, and the important retry caveat is placed second, giving the agent the critical operational detail without burying it.

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?

For a read-only detail lookup with a fully documented schema, the description covers the return fields and the key failure mode. There is no output schema, but the description compensates by listing what the tool returns. Nothing critical for invoking this tool correctly is missing.

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 fully documents actionName, packageName, activationId, and platform. The description adds no additional parameter-level detail beyond what the schema already provides, so the baseline score of 3 is appropriate.

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?

The description opens with a specific verb and resource — 'Get one action activation' — and enumerates the exact contents returned: result payload, status, success flag, logs, start/end/duration. The word 'one' distinguishes it from list-style siblings like ncloud_functions_get_action_activations, making the purpose unmistakable.

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 description gives clear contextual guidance: right after an invocation, the detail may return 80322 ACTION_ACTIVATION_NOT_FOUND for 30-40 seconds and the agent should retry. It does not explicitly name alternatives or state when not to use the tool, but the timing context strongly implies this is the detail-retrieval step after an invocation.

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