ncloud_get_ids_event_detail

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

The annotation readOnlyHint=true already covers the safety profile, so the description adds value by noting the subscription constraint, which is a behavioral prerequisite. It does not describe the return format or potential errors, but the annotation lowers the bar. This additional context about access eligibility is meaningful beyond the schema.

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 two concise sentences. It front-loads the action and resource, then adds the subscription constraint. Every sentence carries useful information with no redundancy or filler.

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?

There is no output schema, so the description should ideally indicate what 'detailed information' includes. The description is adequate for a simple read operation with one well-defined parameter, but the response structure and any notable fields (e.g., event time, source IP) are left unspecified. This is a clear gap for a 'get detail' tool.

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%: the parameter 'ticketId' is clearly described as 'The IDS event ticket ID to get details for'. The description adds no further parameter semantics, so the schema carries the full burden. Baseline 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 a specific verb ('Get') and resource ('IDS intrusion detection event'), clearly distinguishing it from list-type sibling tools like ncloud_list_ids_events. It also names the exact object (specific event) and the service (Security Monitoring), so the agent knows precisely what the tool does.

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 states a clear eligibility requirement ('Only for users subscribed to the Security Monitoring service'), which guides when the tool can be used. It implies that this tool is for retrieving details of a specific event, contrasting with listing tools, but it does not explicitly name alternatives or exclude cases 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.