ncloud_ses_get_import_history

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

The readOnlyHint=true annotation indicates a safe read operation, and the 'Get' verb is consistent. The description adds minimal context (specific resource scope) but does not disclose any additional behavioral traits like return format, pagination, or filtering behavior. With annotations covering the safety profile, this is acceptable but not rich.

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, concise sentence that contains no filler or redundant information. Every word contributes to the meaning.

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 simple read-only history lookup with one parameter and no output schema, the description is mostly sufficient. However, it omits any detail about what the history includes (e.g., status, timestamps, import results), which would help the agent understand the tool's full scope. Still, the simplicity of the operation lowers the burden.

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 only parameter, serviceGroupInstanceNo, is fully described in the schema as 'Cluster instance number' (100% coverage). The description adds no additional parameter semantics beyond referencing the cluster, so the baseline of 3 applies.

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 data import history for a Search Engine Service cluster, with a specific verb and resource. It is distinct from sibling tools like ncloud_ses_run_import and ncloud_ses_stop_import, though it does not explicitly differentiate itself from other history getters.

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?

No guidance is provided on when to use this tool versus alternatives such as ncloud_ses_run_import, ncloud_ses_stop_import, or ncloud_ses_get_import_buckets. The description simply states what it does, 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.