ncloud_functions_get_activations

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

Annotations already mark readOnlyHint=true, so the read-only nature is covered. The description adds value by specifying the default time window ('last month') and the returned fields, which goes beyond annotations. No contradictions.

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?

A single, information-dense sentence that front-loads the primary purpose and scope. No wasted words, and the key details are immediately accessible.

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 covers the core functionality and mentions key return fields, but does not explicitly state that results are paginated (despite pageNo/pageSize parameters) or describe the full response envelope. With no output schema, this is a notable gap for an agent expecting complete return structure.

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%, with detailed parameter descriptions for end, start, pageNo, pageSize, and platform. The description adds no extra semantics beyond what the schema provides, so it meets the baseline for high coverage.

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 specific verb ('List') with a clear resource ('all action activations across the account') and defines scope ('from the last month'). It lists key return fields (activationId, duration, status, totalCount) and distinguishes from siblings like ncloud_functions_get_action_activations by the 'across the account' phrasing.

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 use for account-wide activation listings, contrasting with action-specific or trigger-specific siblings. It does not explicitly name alternatives or state when not to use this tool, but the scope is clear enough for an agent to infer the right selection.

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