get_dns_record

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

Annotations already declare readOnlyHint=true, so the read-only nature is structured data. The description merely restates the operation and adds no behavioral context such as error behavior, permissions, response shape, or side effects. It provides no value beyond what the annotation already communicates.

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, short sentence that directly states the operation. Every word is meaningful, and the core action and resource are front-loaded without any redundancy.

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?

The simple two-parameter schema and readOnlyHint annotation cover the essential invocation requirements. However, with no output schema, 'details' is vague and the agent cannot know what fields the response will contain. This is adequate but leaves a minor gap.

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 100%, with both zone_id and record_id clearly documented. The description adds no parameter-level meaning beyond restating the zone context, so baseline 3 is appropriate.

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 a specific verb and resource: get details of a specific DNS record in a zone. The singular 'specific' distinguishes it from sibling list tools like list_dns_records and list_dns_zone_records without any ambiguity.

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 verb and resource imply this tool is for fetching a single DNS record once its IDs are known, but the description gives no explicit when-to-use guidance or exclusions. It does not mention that list_dns_records or list_dns_zone_records should be used to discover record IDs first.

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