dnssec_list

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

The readOnlyHint annotation already declares this as a safe read operation, and the description does not contradict that. The description adds the domain scoping, but this is already present in the schema. No additional behavioral traits (e.g., pagination, error handling) are disclosed, but the simple nature of the tool and the annotation reduce the burden.

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, tightly worded sentence ('List DNSSEC records for a domain.') that communicates the essential purpose with no redundancy or superfluous details.

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 read-only list tool with one parameter and an output schema, the description adequately covers the core action and scope. However, it could be slightly more complete by explicitly noting that this is distinct from dns_list (which lists regular DNS records), helping agents disambiguate between the two similar-sounding tools.

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?

The schema has 100% coverage for the 'domain' parameter, including an example. The description's phrase 'for a domain' merely restates the schema parameter without adding extra meaning, validation rules, or edge-case guidance.

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 ('DNSSEC records'), clearly distinguishing it from sibling tools like dns_list (regular DNS records) and dnssec_create/delete. It precisely states the tool's scope in a single, unambiguous phrase.

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 provides clear context that this tool is for listing DNSSEC records, implying it should be used when DNSSEC-specific data is needed. However, it does not explicitly mention alternatives or exclusions relative to dns_list, so it lacks an explicit 'vs' statement.

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