dnsSecListRecords

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

With no annotations, the description carries the full burden. 'List' makes clear this is a read operation with no mutation, which is useful, but nothing is disclosed about response format, pagination, errors, or whether DNSSEC must already be enabled. The description is sufficient for a simple list call but lacks deeper behavioral detail.

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 states the action and resource without wasted words. The API reference link is a compact, useful addition that does not clutter the description.

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?

The tool is simple with one required parameter and no output schema, but no annotations exist to cover safety or side effects. The description does not mention return values, prerequisites, or how it differs from related tools beyond the DNSSEC qualifier. The external link helps but may not be reliably accessible to an agent, so the description itself is only partially complete.

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% and the only parameter, 'domain', is adequately documented in the schema. The description adds no extra meaning beyond the schema; it merely restates that the action is 'for a domain'. This matches the baseline of 3 for high schema coverage.

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 ('List') and resource ('DS (DNSSEC) records') with a clear scope ('for a domain'). It explicitly distinguishes this from the sibling dnsListRecords by specifying DNSSEC DS records, making the tool's purpose immediately 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 phrase 'List DS (DNSSEC) records' implies this is the read-only counterpart to dnsSecAddRecord and dnsSecDeleteRecord, but it never explicitly states when to choose this over dnsListRecords or provides any exclusions. The API reference link offers external documentation but no in-description routing guidance.

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