ncloud_sourcedeploy_get_canary_analysis_report

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

The readOnlyHint: true annotation matches the 'Get' verb, so no contradiction. The description does not provide additional behavioral context beyond what annotations already convey, such as error behavior, response contents, or permissions. With annotations covering safety, this is acceptable.

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, front-loaded sentence with no unnecessary words. It is concise but slightly under-specified; however, it is not verbose or bloated. It earns its place.

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 there is no output schema, the description should at least hint at what the report contains, but it does not. It also lacks context about the canary analysis workflow, such as how to get step numbers or how this report relates to canary approval/rejection. This is minimal for a tool with 4 required parameters.

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 coverage is 100%, so a baseline of 3 is appropriate. The description adds no extra meaning beyond the schema, such as whether stepNo is 0-based or 1-based, or any format expectations. The parameter descriptions in the schema are sufficient.

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), the resource (canary analysis report), and the scope (for a specific step). It distinguishes itself from siblings like ncloud_sourcedeploy_get_canary_analysis_steps, which retrieves all steps, by focusing on a single step's report.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives, how to obtain the stepNo, or any prerequisites such as first calling get_canary_analysis_steps. It only implies the tool is for retrieving a report for a known step.

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