dns_get_record

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

With no annotations provided, the description carries the burden. It correctly indicates a read operation ('Get') but doesn't disclose additional behaviors like error handling when the record ID is invalid or missing. However, the presence of an output schema partially compensates for this gap.

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?

A single, concise sentence that contains no extraneous information. It is front-loaded with the verb and resource, making it efficient for an agent to parse.

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 operation with one required parameter and an output schema, the description provides sufficient information to understand the tool's core function. It does not cover edge cases or authentication, but given the simplicity, it is adequate.

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?

The description adds minimal context for the parameter by stating 'by ID', which aligns with the required 'record_id' parameter. With 0% schema description coverage, this aids understanding but doesn't fully compensate for the absence of parameter documentation.

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 verb 'Get' and resource 'a single DNS record' with the method 'by ID'. It distinctly differentiates from sibling tools like dns_list_records (lists all) and dns_create_record (creates), making it unambiguous.

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 implies the tool should be used when fetching a specific DNS record by its ID. While it doesn't explicitly state when not to use it, the sibling tool dns_list_records provides the alternative for bulk retrieval, so usage context is clear.

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