List DNS records

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

Beyond annotations (readOnlyHint, openWorldHint), the description reveals the domain filtering behavior and automatic IDN normalization. This adds useful context about input processing. It does not mention output characteristics, but annotations cover safety and non-determinism.

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 concise sentences, front-loaded with the core purpose, then the parameter condition. No redundant information; every word earns its place.

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 list operation with one optional parameter and annotations covering safety and open world, the description is mostly complete. It specifies what records are listed and how to filter, though it omits details like return format or pagination, which are not critical but could be helpful.

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 parameter description already explains the domain is optional and for filtering, including IDN normalization. The tool description merely restates this, adding no new meaning beyond the schema.

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 clearly states the tool lists DNS records from the server, and mentions optional domain filtering. The verb 'list' and resource 'DNS records' are specific. While it implicitly differentiates from sibling tools like create/delete/update, it does not explicitly distinguish from them, so not a 5.

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 indicates when to use the optional domain parameter but provides no guidance on when to use this tool versus alternatives (e.g., use this for viewing, not modifying). The usage context is implied but not explicit.

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