List DNS Records

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

The readOnlyHint annotation already signals this is a safe read operation, so the bar is lower. The description adds minimal behavioral context beyond the schema, such as the ability to filter by type, name, or content, but these filters are already documented in the input schema. No additional side effects, rate limits, or auth requirements are disclosed, nor is the return format described.

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 three short sentences, front-loaded with the action and resource, then filters, then use case. Every sentence earns its place with no fluff or repetition.

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?

Given the tool's moderate complexity (12 params) and the schema's full coverage of parameter details, the description adequately covers purpose, filters, and a key usage pattern. It does not describe return values or pagination, but the schema covers pagination parameters and a list return is intuitive. A brief mention of output could improve completeness, but it's not critical.

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% for all 12 parameters, so the schema already provides full meaning. The description mentions three filters (type, name, content) which are prominent, but does not add value beyond the schema. 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 uses a specific verb ('List') and resource ('DNS records for a zone'), clearly distinguishing it from sibling tools like get_dns_record (single record) or create/update/delete. The sentence 'Use this to find existing records before creating or updating them' further differentiates its role.

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 explicitly states when to use the tool: 'Use this to find existing records before creating or updating them.' This provides clear context. However, it does not name alternatives or mention when not to use it, such as when retrieving a single record via get_dns_record.

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