List DNS records

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

No annotations provided, so description carries full burden. It only states 'Get DNS records' without disclosing permissions, pagination, rate limits, or whether record types are filtered. The alias might confuse agents expecting a settings retrieval tool.

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 sentence, which is concise but lacks structure. The parenthetical alias adds minor value but could be misleading. Front-loading of key verb and object is good, but overall it feels incomplete.

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 list tool with 2 parameters and no output schema, the description covers the basic purpose. However, it lacks details on output format, pagination, and error handling, which would be helpful for the agent.

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 50%: zone_host is described, record_id is not. The description adds no additional meaning to parameters. It does not clarify that record_id is optional for listing all records or that it filters results.

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 for a zone, distinguishing it from sibling tools that add, delete, or update records. The alias 'get_dns_settings' reinforces its reading nature. However, it could be more precise about the scope (e.g., all records or filtered).

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?

No guidance on when to use this tool versus alternatives like dns_search or other list tools. The description does not mention prerequisites or context (e.g., zone must exist).

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