list-me-dns-records

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

Annotations already provide readOnlyHint and openWorldHint, and description adds 'Read-only view of the authoritative zone' reinforcing safety. No contradictions; description adds context about zone and authoritative nature.

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 concise sentences, no fluff. Front-loaded with main action and key qualifiers (domain ID, filtering, pagination). Every phrase earns its place.

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 no output schema and simple list operation, description covers purpose, parameters, and read-only behavior. Could add that it returns a list of DNS record objects, but not essential for agent invocation since schema is detailed.

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 baseline is 3. Description adds value by stating filtering by 'record type or FQDN' and pagination, which synthesizes the purpose. Not adding much beyond what schema already says, but sufficiently clear.

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 explicitly states 'List DNS records for a specific owned domain', includes filtering and pagination capabilities, and distinguishes from sibling tools like list-me-dns-records-by-fqdn by mentioning domain ID and read-only nature. Verb 'List' and resource 'DNS records' are clear.

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?

Describes when to use (list records, filter, paginate) and hints at read-only use (vs. create/delete). However, does not explicitly mention alternatives like list-me-dns-records-by-fqdn or when not to use this tool.

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