ncloud_sourcedeploy_get_canary_analysis_steps

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

The annotation readOnlyHint=true already indicates a safe read operation. The description adds no extra behavioral context, such as ordering, pagination, or dependencies. It is consistent with the annotation but offers minimal additional transparency beyond the resource identification.

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, focused sentence that conveys the essential operation without unnecessary words. It is front-loaded and easy 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?

For a simple read-only getter with self-explanatory parameters and a readOnlyHint, the description sufficiently identifies the resource and distinguishes from the report tool. It lacks detailed context about the step list's structure or prerequisites, but given the simplicity, it is reasonably 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?

The schema provides full descriptions for all three parameters (IDs of stage, project, scenario), covering 100% of parameters. The description does not add further semantic meaning beyond the generic 'for a deployment', so it meets the baseline but does not exceed it.

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 the action ('Get') and the specific resource ('canary analysis step list for a deployment'), which distinguishes it from sibling tools like ncloud_sourcedeploy_get_canary_analysis_report. It is direct and unambiguous.

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 usage when retrieving the step list for a canary analysis, but it does not explicitly compare with alternatives such as the canary analysis report tool. No exclusions or when-not-to-use guidance is provided, so it remains at an implied level.

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