ncloud_dns_list_records

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

Annotations already declare readOnlyHint=true. The description adds no behavioral context beyond what annotations provide, such as authorization needs, rate limits, or side effects. It only restates the read-only nature implicitly through 'list'.

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 sentence of 10 words. It is direct, front-loaded, and contains no extraneous information. Every word contributes to the core 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?

Given the rich schema and annotations, the description is minimally adequate. It mentions the domain and pagination but does not hint at optional filtering parameters (recordType, searchContent) or response structure. The tool has no output schema, so more contextual guidance would be beneficial.

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% for all 5 parameters. The description does not add additional meaning beyond the schema; it only mentions 'with pagination' which relates to page and size parameters already documented in the schema.

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 the action (list), the resource (DNS records for a specific Global DNS domain), and includes 'with pagination'. It distinguishes from sibling DNS tools like ncloud_dns_list_domains by specifying 'for a specific Global DNS domain'.

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 context by referencing a specific domain, but it does not explicitly state when to use this tool versus alternatives like ncloud_dns_list_domains or ncloud_dns_create_records. No exclusion criteria or alternative tools are mentioned.

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