List DNS Records

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds behavioral detail about pagination (uses pagination, can fetch all pages automatically), which is useful beyond what annotations provide. No contradictions.

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 two short sentences with no fluff. It front-loads the purpose ('List all DNS records for a domain') and then adds the pagination detail concisely.

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?

Given the tool has 5 parameters, no output schema, and annotations provide safety context, the description is adequate but incomplete. It lacks details on sorting (orderBy), what fields are returned, or how fetchAll works in depth. The openWorldHint partly mitigates this.

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 80%, so baseline is 3. The description mentions pagination, which relates to skip, take, and fetchAll, but does not add new semantics beyond schema descriptions. OrderBy is not explained, but the schema provides enough via enum values.

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 'List all DNS records for a domain,' specifying the verb 'list,' the resource 'DNS records,' and the scope 'for a domain.' This distinguishes it from sibling tools for creating, saving, or deleting records.

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 mentions pagination and automatic fetching, which hints at usage for reading multiple records, but it does not explicitly state when to use this tool versus alternatives like creation tools or how to handle pagination edge cases. The context is implied but not spelled out.

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