ncloud_update_extended_disable

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

The annotations already declare idempotentHint=true and destructiveHint=false, establishing the safety profile. The description adds little beyond the core action; it does not explain consequences of disabling extended metrics or what happens to collected data. However, the annotation coverage reduces the burden, and the action is clearly non-destructive per the annotations.

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, concise sentence that states the action and target without redundancy. Every word contributes to clarity, making it highly efficient.

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 tool with only two fully described parameters, a clear purpose, and supportive annotations, the description is adequately complete. It does not mention return values or side effects, but the simplicity and schema coverage make it sufficient for invocation.

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?

Both parameters (cw_key and instanceIds) are fully described in the schema with 100% coverage. The description adds no additional meaning beyond the schema's field descriptions, so the baseline of 3 is appropriate.

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 'Disable' and specifies the resource 'Extended Metric collection for instances in Cloud Insight', clearly identifying the action and scope. It distinguishes itself from the sibling tool ncloud_update_extended_enable by describing the opposite operation.

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 implies the use case—disabling extended metrics for given instances—but does not explicitly state when to use this tool versus alternatives or mention any exclusions or prerequisites. There is no reference to the complementary enable tool, though the context makes the purpose fairly evident.

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