ncloud_sourcedeploy_get_canary_analysis_report

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

Annotations include 'readOnlyHint: true,' and the description confirms a read operation ('get'). However, the description does not add behavioral context beyond the annotation, such as what data the report contains, whether it requires a prior step, or rate limits. With annotations covering the safety profile, a score of 3 is adequate.

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, clear sentence with no unnecessary words. It is concise and front-loaded, though it could include more context without losing conciseness.

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 the tool's simplicity (4 required params, no output schema, annotations present), the description adequately covers the purpose. However, it could mention that the report is associated with a canary analysis step, which adds minor missing context.

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?

All four parameters are described in the schema (100% coverage), with brief descriptions like 'ID of the deployment project.' The description does not add any additional meaning beyond the schema, so the baseline score of 3 applies.

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 'Get the canary analysis report for a specific step,' specifying the verb 'Get,' the resource 'canary analysis report,' and the scope 'for a specific step.' This distinguishes it from siblings like 'ncloud_sourcedeploy_get_canary_analysis_steps,' which retrieves step details rather than the 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?

The description lacks any guidance on when to use this tool versus alternatives, such as when to retrieve the report after a canary analysis step is completed. No exclusions, prerequisites, or sibling comparisons are provided.

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