ncloud_list_mysql_events

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

The readOnlyHint annotation already declares the safe read-only nature. The description adds the context that it returns 'event history' but does not disclose additional behavioral traits such as pagination limits, event types covered, or whether events are returned chronologically. It does not contradict the annotation.

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, tightly worded sentence that states the action and scope immediately. No filler or redundancy. It is 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 simple read-only list operation with only two parameters and no output schema, the description is nearly sufficient: it says what is listed and for which resource. It could improve by describing the nature of events (e.g., lifecycle events, monitoring events) or indicating the response format, but the core invocation context is complete.

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%: both cloudMysqlInstanceNo and regionCode have clear descriptions in the schema. The tool description adds no parameter-specific meaning beyond naming the instance. Baseline 3 applies because the schema already documents both parameters.

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 ('List') and clearly identifies the resource ('event history') scoped to a 'Cloud DB for MySQL instance'. This distinguishes it from sibling MySQL tools like ncloud_list_mysql_databases, ncloud_list_mysql_users, and ncloud_list_mysql_logs, and from unrelated event tools such as ncloud_list_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 when to use it: whenever you need event history for a specific MySQL instance. However, it does not explicitly contrast it with alternatives like ncloud_list_mysql_logs or mention conditions, prerequisites, or exclusions. The usage context is clear but not elaborated.

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