Get domain parent DS

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds one useful trait beyond the schema—the domains:read permission requirement for API keys—but says nothing about pagination, result size, or what an empty result means.

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?

Two short sentences with the core purpose front-loaded and no wasted prose. The permission requirement is appended efficiently rather than padding the lead sentence.

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 single-parameter read-only tool with full schema coverage and annotations covering safety, the description is nearly sufficient, and the mention of DS records implies the return content. It stops just short of describing the returned record shape (key tag, algorithm, digest), which for a no-output-schema tool would have been the final useful addition.

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% and domain_id is already documented as 'Owned domain ID from list_domains', so the baseline is 3. The description adds no format, source, or constraint detail about the parameter beyond what the schema provides.

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 names a specific verb (List) and a precise resource (parent-zone DNSSEC DS records for an owned domain), which cleanly separates it from the add_domain_parent_ds and delete_domain_parent_ds siblings. An agent knows exactly what this retrieves without opening any schema.

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?

Usage is implied by 'for an owned domain' and the tool's read-only nature, and the description supplies a prerequisite (domains:read with an API key). However, it never states when to use this versus alternatives such as get_domain or the add/delete DS tools, so routing is left to inference.

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