ncloud_list_av_events

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

readOnlyHint is already provided, indicating a safe read operation. The description adds the subscription prerequisite but does not disclose rate limits, pagination, or response behavior. Since the annotation covers the safety profile, a score of 3 is appropriate.

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?

Single succinct sentence with no filler. Clearly front-loaded with the verb and resource.

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 read-only list tool with comprehensive schema descriptions and a readOnlyHint annotation, the description sufficiently identifies the data source, event type, and subscription requirement. It doesn't detail output structure, but no output schema is provided and the tool type is well-understood.

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?

Input schema has 100% description coverage across all 10 parameters, so parameter meaning is already well-documented. The description itself does not add parameter semantics, so baseline score 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 lists Anti-Virus malware detection events from Security Monitoring, using the specific verb 'List' and a specific resource type. It distinguishes itself from sibling event-listing tools (e.g., ncloud_list_ids_events, ncloud_list_waf_events) by focusing on AV events.

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 usage context (AV malware detection events) and adds an eligibility constraint (Security Monitoring subscription). However, it does not explicitly contrast with alternative event-listing tools or provide when/when-not guidance beyond the subscription requirement.

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