search_dns_access_lists

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent understands this is a safe read operation. The description adds 'with pagination,' which is a behavioral trait beyond the schema, but it's minimal and mostly echoes the page/page_size parameters.

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 concise sentence that states the core purpose and a key feature (pagination) with no wasted words. It front-loads the essential information effectively.

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 this is a simple search tool with a complete input schema, safety annotations, and an output schema, the description provides sufficient context for a basic search operation. It could mention what an access list is or how it differs from BIND access lists, but that's not necessary for an agent to invoke it correctly.

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% and each parameter (page, sort_by, page_size) is already well-described in the schema. The description adds no additional parameter meaning beyond noting pagination, which is already represented by the page and page_size parameters.

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 tool searches DNS Resolver access lists, using a specific verb ('search') and a specific resource. It distinguishes from sibling tools like search_bind_access_lists by explicitly naming 'DNS Resolver'.

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?

Usage is implied by the tool name and description: it's a read-only search for DNS Resolver access lists. However, no explicit alternatives or when-not-to-use guidance is provided, leaving the agent to infer context from the name and sibling list.

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