ncloud_functions_delete_trigger

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

Annotations already mark this as destructive and idempotent, but the description adds valuable context: the operation is 'permanent' (irreversible) and requires confirm=true to execute, which is a critical behavioral gate not fully conveyed by the destructiveHint alone. This goes beyond what annotations provide.

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 with a warning emoji, a clear action, and the critical confirmation instruction. Every word serves a purpose; no filler or redundancy.

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 destructive operation with complete schema coverage and no output schema, the description provides the essential information: what it deletes and the safety confirm gate. It doesn't mention error behavior when confirm is false or prerequisites, but these are reasonable omissions for this tool's simplicity.

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 schema already documents all three parameters (confirm, platform, triggerName) with clear descriptions. The tool description only reiterates the confirm=true requirement already present in the schema, adding no new meaning to any parameter.

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 action ('Permanently delete') and the specific resource ('a Cloud Functions trigger'), making it unambiguous and distinct from sibling tools like ncloud_functions_create_trigger or ncloud_functions_list_triggers. The verb+object structure precisely conveys 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?

No explicit guidance is provided about when to use this tool versus alternatives, or any prerequisites such as unlinking trigger actions first. The description only states what the tool does, not the circumstances for use or exclusions. The confirm flag instruction is operational guidance but not about tool selection.

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