ncloud_datacatalog_get_scanner_histories

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds no behavioral context beyond that—e.g., it does not mention pagination support (pageNo, pageSize) or that a time range (fromTimestamp, toTimestamp) is required. 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 4-word sentence, which is concise but perhaps too terse. It is front-loaded with the purpose, but a slightly longer description could provide essential context without becoming 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?

With no output schema, the description should clarify what the tool returns (e.g., list of execution records with status, duration). It also does not mention that fromTimestamp and toTimestamp are required for time-range filtering. This incompleteness reduces the tool's usability.

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?

All 6 parameters are fully described in the input schema (100% coverage). The tool description does not add any extra meaning or usage hints beyond what the schema provides, so it meets the baseline but does not enhance understanding.

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 scanner execution history' clearly states the verb (get) and the resource (scanner execution history), effectively distinguishing it from sibling datacatalog tools like ncloud_datacatalog_get_scanners and ncloud_datacatalog_get_scanner. However, it lacks additional specificity about what the history includes (e.g., statuses, timestamps).

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_datacatalog_get_scanner or ncloud_datacatalog_run_scanner. It does not mention any prerequisites, exclusions, or contextual hints for selecting this tool over others.

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