ncloud_functions_delete_trigger

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

While destructiveHint is already in annotations, the description adds 'Permanently' and explains the confirm=true gate, which is behavioral context beyond the annotation. This clarifies irreversibility and the required explicit consent. It does not contradict the idempotentHint, and no auth or rate-limit details are needed at this level.

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 sentences, front-loaded with the destructive warning and purpose, then the confirmation instruction. There is no filler, and every word contributes to safe invocation. The emoji and uppercase 'Destructive' effectively draw attention.

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 3-parameter destructive operation with full schema coverage and annotations carrying the safety profile, the description is complete. It adds the one non-obvious requirement (confirm=true) and the permanence of the action. No output schema exists, so return-value explanation is unnecessary, and nothing needed for correct invocation is missing.

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 the baseline is 3. The description restates the confirm parameter's semantics already present in the schema ('Must be true to actually execute the destructive operation') without adding new meaning for triggerName or platform. It adds no value beyond what the structured schema already provides.

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 ('delete'), resource ('Cloud Functions trigger'), and permanence ('Permanently'). This clearly differentiates the tool from sibling functions like ncloud_functions_delete_package or ncloud_functions_delete_action. The tool name and description align without tautology.

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 gives a critical invocation condition ('Set confirm=true to execute') but does not say when to use this tool versus alternatives, nor provide exclusions or prerequisites. It relies on the tool name and schema to convey the target resource, and omits any guidance about when deletion is appropriate or how it contrasts with deleting packages/actions.

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