ncloud_delete_cache_config_group

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

The description includes a warning emoji and states 'Destructive' and 'Permanently delete,' which aligns with the destructiveHint annotation. It also adds the requirement for confirm=true, providing useful behavioral context beyond what annotations offer.

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 extremely concise, with a single sentence plus a warning emoji. It is front-loaded with the warning, making it efficient for an AI agent to parse.

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?

Given the destructive nature and the presence of annotations, the description is complete enough. It covers the key behavior and required parameter. There is no output schema, so return values are not expected.

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 reinforces that confirm must be true but does not add meaning beyond the schema's parameter descriptions.

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 'Permanently delete a Cloud Cache config group,' specifying the verb (delete) and the resource (Cloud Cache config group). It is specific and distinguishable from sibling tools that deal with other resources.

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 provides a usage guideline ('Set confirm=true to execute') but does not explicitly state when to use this tool versus alternatives or when not to use it. The guidance is minimal.

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