ncloud_functions_get_action_activations

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

Annotations indicate readOnlyHint=true, which already conveys the tool is a read operation. The description adds that it retrieves 'history' but does not disclose additional behavioral traits like pagination, filtering (though parameters exist), or the nature of the response. No contradiction with annotations.

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, focused sentence with no extraneous information. It is concise and front-loaded, but could potentially include additional context about the output or usage without being verbose.

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?

The description lacks information about the output (no output schema), which is critical for an agent to understand the return format. Given the tool's purpose (history retrieval), describing that it returns a list of activation records would improve completeness. The description is too brief given the complexity of the input schema and lack of output schema.

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 covers 100% of parameters with descriptions. The description does not add meaning beyond the schema, so it meets the baseline for high coverage. No extra parameter guidance is provided.

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 retrieves activation (execution) history for a specific action, using a specific verb ('Get') and resource. However, it does not explicitly differentiate from sibling tools like ncloud_functions_get_activations or ncloud_functions_get_action_activation_detail, which could lead to confusion for an AI agent.

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 when to use ncloud_functions_get_activations vs this tool. No exclusions, prerequisites, or caveats are mentioned, leaving the agent to infer usage context.

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