ncloud_update_extended_enable

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

Annotations already declare idempotentHint=true and destructiveHint=false, covering the safety profile. The description accurately states the primary effect but adds no extra behavioral context such as billing impact, propagation delay, or prerequisites beyond what annotations and schema 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?

Single sentence that is front-loaded with the action ('Enable') and contains no filler. Every word contributes to understanding the tool's purpose and scope.

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 idempotent enable operation with fully documented required parameters and a non-destructive annotation, the description is adequately complete. It does not mention how to verify the result, but the sibling ncloud_get_extended_status can be inferred and no output schema is provided.

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%: cw_key is identified as product key and instanceIds as comma-separated server instance numbers. The description does not add further parameter meaning, but the schema is sufficient for selecting and invoking with correct values.

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 uses a specific verb 'Enable' with a clear resource 'Extended Metric collection' and target context 'instances in Cloud Insight'. It clearly differentiates from the sibling ncloud_update_extended_disable by indicating the enabling action.

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 clear context: use it to enable extended metric collection for Cloud Insight instances. It does not explicitly mention alternatives or exclusions, but the counterpart disable tool is identifiable from the name, so no confusion arises.

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