get_dns_hosts

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

No annotations provided, so description carries full burden. It only says 'Get all DNS host records', implying a read operation, but lacks any disclosure about pagination, rate limits, ordering, or what happens if the domain is invalid. No details on return format or count.

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?

Single sentence with no fluff. Every word adds value: action, resource, types, scope. Front-loaded and efficient.

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 read tool with one parameter and no output schema, the description is minimally adequate. However, it does not specify the return format or field structure, which could be important for an agent to process the results. Lacks context about typical results (e.g., array of objects).

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% with a description for 'domain' that matches the tool description. The tool description does not add new meaning beyond the schema; it only restates the example. Baseline 3 is appropriate as schema already documents the parameter well.

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?

Description clearly states the verb 'Get', the resource 'DNS host records', and lists specific record types (A, AAAA, CNAME, MX, TXT, URL). This distinguishes it from sibling tools which are for checking connections, setting records, or retrieving other domain info.

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 vs alternatives. Siblings like 'set_dns_hosts' handle modifications, but the description does not explicitly state that this tool is for reading only or provide any context for choosing it over others.

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