ncloud_ses_get_snapshot_history

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

The readOnlyHint annotation already communicates that this is a safe read operation. The description adds context about the resource type (Search Engine Service cluster) but does not disclose details such as the response structure, pagination, or any filtering behavior. This adds some value but not substantial behavioral context.

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, front-loaded sentence with no unnecessary words. It directly states the operation and target resource, making it highly concise and well-structured.

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 get with one parameter and no output schema, the description conveys the essential information: what is retrieved (snapshot creation history) and for which resource (SES cluster). It does not explicitly describe the return format, but given the simplicity of the tool, this is largely adequate.

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 schema already documents the single parameter 'serviceGroupInstanceNo' with the description 'Cluster instance number' at 100% coverage. The tool description reinforces the cluster context but does not add meaning beyond what the schema provides, so the baseline 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 uses the specific verb 'Get' and clearly identifies the resource as 'snapshot creation history' for a 'Search Engine Service cluster'. This distinguishes it from sibling snapshot tools like ncloud_ses_get_snapshot_buckets or ncloud_get_snapshot_detail, making its 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 clearly implies when to use this tool (when snapshot creation history is needed for an SES cluster), providing clear context. However, it does not explicitly mention alternatives or state when not to use it, which is typically present for a score of 5.

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