ncloud_dns_get_domain_detail

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

Annotations already declare readOnlyHint=true, and the description merely echoes this with 'Get detailed information' without adding context such as what fields are returned, error behavior, or any special constraints. The description provides no behavioral insights beyond what the annotation already communicates.

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 wasted words. It is front-loaded with the action ('Get') and resource ('detailed information') and is appropriately brief for a simple getter tool.

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?

With no output schema, the description should ideally indicate what kind of detailed information is returned (e.g., records, TTL, status). It only says 'detailed information', which is vague. For a simple one-parameter tool with a readOnlyHint, this is adequate but leaves room for improvement.

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% (domainId is described as 'Domain ID to query'). The tool description adds no additional parameter semantics beyond the schema, which is the baseline for high coverage. No further elaboration is provided.

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 uses a specific verb and resource: 'Get detailed information about a specific Global DNS domain.' This clearly differentiates it from sibling tools like ncloud_dns_list_domains (which lists domains) and other DNS operations. The scope is explicit 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 you need details for a specific domain) but does not explicitly state when to use this tool versus alternatives, nor does it name any sibling tools for comparison. Sibling differentiation is inherent from the name, but no direct guidance or exclusions are provided.

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