ncloud_functions_list_triggers

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

The description aligns with the readOnlyHint annotation (listing is read-only) and adds the return format (name + type). However, it does not disclose additional behavioral traits such as pagination, rate limits, or the fact that it lists triggers across the current region/context. With annotations covering safety, a 3 is appropriate for the modest added value.

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, front-loaded sentence that conveys the action and return fields with zero waste. Every word contributes to understanding the tool's purpose.

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 list tool with one optional parameter and no output schema, the description provides the essential information: what it lists and what fields are returned. It is complete for an agent to invoke it correctly, as the schema covers the only parameter.

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% for the 'platform' parameter, so the schema already documents it fully. The description does not add any additional parameter context, matching the baseline of 3 when the schema carries the semantic burden.

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 states a specific verb ('List'), resource ('Cloud Functions triggers'), and the returned fields ('name + type'). It clearly distinguishes from siblings like ncloud_functions_list_actions (actions) and ncloud_functions_get_trigger (single trigger) by specifying the scope as 'all' and the resource type.

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 (list all triggers) but does not explicitly state when to use this tool versus alternatives like ncloud_functions_get_trigger for a specific trigger. It lacks explicit exclusions or alternative routing, which is a gap given the large sibling set.

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