ncloud_secret_list_triggers

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

The readOnlyHint=true annotation already establishes this is a safe read, lowering the descriptive burden. The description usefully defines the trigger concept (Cloud Functions triggers driving rotation) but adds nothing about pagination, result shape, or scoping constraints beyond what the schema parameter implies.

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?

A single tight sentence with no waste, and the key disambiguating detail (Cloud Functions triggers for rotation) is front-loaded. It earns its place, though it could carry a bit more routing information at the same length.

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 with no output schema, the description is sufficient to call correctly. However, given the dense family of ncloud_secret trigger siblings, it omits any hint about when this list is needed in a rotation workflow, leaving a gap an agent must infer.

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% and the single keyIsolation parameter is fully documented with enum values and host implications, so the baseline is 3. The description does not reference keyIsolation at all, adding no meaning beyond the schema.

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?

States a specific verb+resource (list rotation triggers) and clarifies what a trigger is here ('Cloud Functions triggers that can run automatic secret rotation'). An agent can tell it apart from generic trigger tools on the surface, but it does not explicitly distinguish itself from adjacent siblings like ncloud_secret_update_rotation_trigger or ncloud_functions_list_triggers.

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?

No when-to-use guidance, prerequisites, or alternatives are given. The agent learns the domain (secret rotation) but nothing about when this list tool is the right call versus the related trigger-management siblings.

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