ncloud_get_monitor_group

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

The readOnlyHint=true annotation already tells the agent this is a pure read with no side effects, so the bar for the description is lower. It adds nothing beyond that — no note on whether a missing/unauthorized monitorGroupId errors versus returns empty, no mention of which prodKey namespace applies. Adequate but thin against an annotation that carries the safety profile.

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?

A single front-loaded sentence with no filler or redundancy. It is well sized for the operation, though it is so terse that it leaves useful routing information unstated.

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 two-parameter read tool with full schema documentation and a readOnlyHint, the description is minimally sufficient. There is no output schema, so the description could usefully say what 'detailed information' includes (endpoint, thresholds, status) but does not, leaving a modest gap.

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 description coverage is 100%: prodKey is documented as the cw_key the group belongs to and monitorGroupId as the ID to retrieve. The description adds no format, sourcing, or constraint detail beyond the schema, so the baseline 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 names a specific verb and resource: 'Get detailed information about a specific Cloud Insight monitoring target group.' An agent knows this is a read of a single monitor group, not a list or a mutation. It does not, however, distinguish itself from siblings like ncloud_list_monitor_groups or ncloud_get_metrics_group, which are close in name and scope.

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?

There is no when-to-use guidance and no named alternative. The word 'specific' implies a single-record lookup requiring an identifier, but the description never contrasts this with ncloud_list_monitor_groups (browse by prodKey) or with the metrics-group equivalents, so the agent must infer routing from names alone.

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