ncloud_list_ids_events

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

Annotations already declare readOnlyHint=true, and the description aligns with a read operation. It adds the subscription requirement, which is useful behavioral context beyond annotations, but does not disclose other behaviors like default pagination or error conditions.

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 short sentences, front-loaded with the primary action and scope, and contains no redundant or filler content. Every sentence adds information.

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?

The description identifies the service scope and subscription prerequisite, while the schema documents parameters and defaults. However, there is no output schema and no mention of return format, pagination behavior, or how events are ordered, leaving some gaps for a listing tool with 10 parameters.

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%, so all 10 parameters are already documented in the schema. The description adds no parameter-specific meaning beyond 'list events', but since schemas carry the full load, a 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 clearly states the tool lists IDS intrusion detection events from Security Monitoring, using a specific verb and resource. It distinguishes from sibling event-list tools by specifying 'IDS' and 'Security Monitoring', though it does not explicitly name alternative tools.

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 a clear usage restriction ('Only for users subscribed to the Security Monitoring service'), indicating when not to use it. However, it does not mention alternatives or explicitly state when to use this tool over other event list tools.

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