dns_create

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

The annotation idempotentHint: false already informs the agent that repeated calls create multiple records, covering the key behavioral trait. The description adds no further context, such as side effects, validation behavior, or prerequisites, but it does not contradict the annotation.

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, clear sentence with no filler. It is front-loaded with the action and resource, earning a perfect score for conciseness.

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?

With a thorough schema, an output schema, and a simple operation, the description is adequate. It lacks some context like domain existence prerequisites, but the schema and annotations cover the essentials, making it complete enough for an agent to use effectively.

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%, so parameter meanings are fully documented. The description itself adds no parameter semantics, but the schema carries the burden, resulting in a baseline 3 score.

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 specific verb ('Create') and resource ('a new DNS record'), clearly distinguishing it from sibling tools like dns_list, dns_edit, and dns_delete. It is unambiguous and accurately describes the operation.

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 verb 'Create' implies use for adding a new record, and the sibling names make it clear that edit/delete are for other purposes. However, there is no explicit guidance on when to use this tool versus alternatives, such as noting that dns_edit should be used for modifying existing records or that creating a duplicate may be prohibited.

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