delete_nlu_connector

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

Discloses destructive nature ('WARNING: Endpoints using this connector will lose NLU functionality') and mutation requirement (dryRun=false), adding value beyond annotations which already indicate destructiveHint=true.

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?

Two concise sentences plus a warning, front-loading key information with no redundant text. Every sentence adds value.

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 delete operation, description covers what, consequences, and parameter usage. No output schema needed; warnings and mutation instructions are 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 already describes both parameters with 100% coverage; description adds practical guidance ('Set dryRun=false to delete') that clarifies parameter usage beyond schema defaults.

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?

Description clearly states 'Deletes a Cognigy.AI NLU connector' with a specific verb and resource, distinguishing it from other delete tools among siblings.

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?

Provides warning about endpoints losing NLU functionality and instructs to set dryRun=false for actual deletion, giving clear usage context. Lacks explicit when-not-to-use or alternatives but is adequate.

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