ncloud_dns_list_records

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds only the pagination behavior, which is already fully described by the schema's page/size parameters. No additional behavioral context, such as result ordering or filtering semantics, is provided beyond the 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?

A single, front-loaded sentence that names the action, the resource, the scope, and the pagination trait with zero filler.

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 read-only list tool with full schema coverage and no output schema, the description is sufficient to select and invoke it. It could be stronger if it hinted at what a record object contains or how the recordType/searchContent filters combine, but nothing needed to call it correctly is missing.

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%, so all five parameters (domainId, recordType, searchContent, page, size) are already documented in the schema. The description's mention of 'pagination' mirrors the schema without adding syntax, defaults, or filter-combination semantics.

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?

States a specific verb and resource ('List DNS records') and scopes it to a specific Global DNS domain, which is unambiguous on its own. However, it does not differentiate itself from the sibling ncloud_dns_list_lb_records, which also lists DNS-related records, so an agent must infer the boundary.

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 phrase 'for a specific Global DNS domain' implies the precondition that a domainId is known, but there is no explicit when-to-use guidance and no alternative tool named (e.g., ncloud_dns_list_lb_records). Usage is inferable rather than stated.

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