add_dns_subdomain

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the mutation and external visibility are already known. The description adds a permission requirement (pdns/edit), which is useful added context, but does not disclose side effects like propagation or whether the operation is idempotent.

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 short sentence with an API hint and permission note; concise and front-loaded with the action. No wasted words, though it could be slightly clearer in structure.

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 4-parameter mutation tool with no output schema, the description covers the basic purpose and permission requirement, but lacks details on return values, failure modes, or interaction with related tools. It is minimally adequate but has clear gaps.

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%, so parameters are already documented in the schema. The description adds no extra parameter meaning beyond what is in the schema (e.g., no format or constraints for 'name' or 'confirm'). Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a clear verb+resource: adding a subdomain to the subdomains table, with an API path hint (pdns/add_subdomain). It distinguishes from siblings like add_dns_domain/add_dns_zone by specifying subdomain, but does not explicitly name the sibling edit_dns_subdomain or others.

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?

It implies usage by stating required permissions (pdns/edit), which gives a precondition, but does not say when to use this tool vs alternatives such as add_dns_record or edit_dns_subdomain. No explicit when/when-not guidance.

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