cf_list_dns

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering safety. The description adds behavioral context by specifying SEO migration use cases, which goes beyond the annotations and helps the agent understand the tool's role.

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?

Two sentences with no fluff: first sentence defines the operation, second lists practical use cases. Every word earns its place; it is as concise as possible without sacrificing clarity.

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?

No output schema exists, so the description should compensate with details about the return format (e.g., fields like name, type, TTL, content). It omits this and does not mention pagination or limits, making it somewhat incomplete for a list tool.

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%, so the schema already describes both parameters ('type', 'zone') adequately. The description does not add any additional meaning or examples beyond what is in the schema, meeting only the baseline.

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 states 'List DNS records for a zone (read-only)' – a specific verb and resource. It further clarifies use cases like verifying canonical host, CNAME flattening, and TXT records during SEO migrations, distinguishing it from sibling tools that manage zones or analytics.

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 usage for verification tasks but does not explicitly state when to use this tool vs alternatives like cf_list_zones or cf_zone_info. No when-not-to-use or alternative naming is provided, leaving some ambiguity.

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