ncloud_functions_get_action_activation_detail

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

Annotations already declare readOnlyHint=true, and the description merely restates the operation ('Get...') without adding behavioral context such as what fields are included, whether the response includes logs, or any pagination/error behavior. It adds no disclosure beyond the name and annotation.

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?

The description is a single, clear sentence with no redundant words or filler. It communicates the core purpose efficiently and front-loads the action.

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 the simplicity of the operation (a read-only get by ID), the description, combined with fully documented parameters and readOnlyHint annotation, provides sufficient context for an agent to select and invoke the tool. Though no output schema exists, the agent can infer the detailed nature of the response from the name and description.

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?

The input schema provides descriptions for all four parameters, including enums for platform and explanations for actionName, packageName, and activationId. Since schema coverage is 100%, the description adds no additional parameter meaning, and a 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 'Get detailed information about a specific action activation' uses a specific verb (get), names the resource (action activation), and specifies granularity (specific, detailed). It clearly distinguishes from sibling tools like list-oriented ones (e.g., ncloud_functions_get_activations) by targeting a single activation.

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 provides no guidance on when to use this tool versus alternatives such as ncloud_functions_get_trigger_activation_detail or ncloud_functions_get_action_activations. There are no usage scenarios, prerequisites, or exclusions stated.

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