ncloud_search_metric_list

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

Annotations already declare readOnlyHint=true, so the description only needs to add behavioral context. It clarifies that this searches 'available monitoring metrics', implying a list of metric definitions rather than data values. No contradictions with annotations.

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 of 11 words, front-loaded with action and resource. No redundant information; every word serves a purpose.

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 list/search tool with one parameter and annotations covering read-only behavior, the description is sufficient. It tells the agent exactly what to expect: search metrics by product key. Could mention typical use case or output shape, but not strictly necessary given the simplicity.

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% with a description for prodKey. The description adds no additional semantics beyond what the schema already provides, meeting the baseline but not exceeding 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?

Clear verb-resource combination: 'Search available monitoring metrics' specifies action and resource. The phrase 'for a specific product' narrows scope. Differentiates from siblings like ncloud_query_monitoring_data (which retrieves metric values) and ncloud_list_metrics_groups (which lists metric groups).

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?

Provides no explicit guidance on when to use this tool versus alternatives like ncloud_query_monitoring_data or ncloud_search_logs. Implies usage when you need to discover available metrics for a product, but lacks when-not statements or direct sibling comparisons.

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