ncloud_functions_get_trigger_activation_detail

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

Annotations already declare readOnlyHint=true, so the description correctly avoids repeating that. It adds a valuable, concrete behavioral caveat about the 80518 error and the ~30-40s retry window, which is beyond structured fields and helps an agent handle failures correctly.

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, no filler. The first sentence states the core purpose with the returned fields; the second delivers a crucial retry tip. Every word earns its place and the key information is front-loaded.

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 single-detail read with three parameters and no output schema, the description covers the essential behavior: what it returns and the transient error condition. It doesn't describe return format, but given the absence of an output schema and the simple scope, it is adequately complete.

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 coverage is 100%, so all parameters are documented. The description adds practical context about activationId specifically—that it may transiently return NOT_FOUND—which is parameter-relevant and not in the schema. This enriches parameter understanding beyond the 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?

The description clearly states the tool gets one trigger activation and lists the exact fields returned (result, status, success flag, logs, start time). This distinguishes it from list tools like ncloud_functions_get_trigger_activations, making the purpose 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?

The description implies it is for retrieving a single activation detail rather than a list, but it does not explicitly name alternatives or state when to prefer this tool over ncloud_functions_get_trigger_activations or similar siblings. The guidance is implicit rather than explicit.

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