ncloud_ses_change_node_spec

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

Annotations (idempotentHint true, destructiveHint false) already convey idempotency and non-destructiveness. Description adds 'change server specifications' which is consistent but does not provide additional behavioral context (e.g., permissions, reversibility, effect on running state).

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, 11 words, front-loaded with the key action. No redundancy or unnecessary detail.

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 that modifies server specifications, more details about constraints (e.g., supported product codes, impact on running instances, return behavior) would be helpful. The 100% schema coverage partially compensates, but the description lacks overall completeness.

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 has 100% description coverage for all 3 required parameters. Description does not add any parameter information beyond what is already in the schema.

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 the verb 'Change', resource 'server specifications', and scope 'nodes in a Search Engine Service cluster'. It distinguishes from read-only siblings like get_node_spec_detail but does not explicitly differentiate from similar mutation tools like change_node_type.

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?

No guidance on when to use this tool versus alternatives (e.g., ncloud_ses_change_node_type, ncloud_ses_change_disk_size). No prerequisites or context provided.

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