list_rrsets

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact, '(all pages)', telling the agent that pagination is handled internally and no cursor loop is needed. It says nothing about authorization requirements, match semantics for filters, or what a result entry contains.

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 short sentences, front-loaded with the resource and scope, with no filler. The parenthetical '(all pages)' is slightly awkward but earns its place by conveying auto-pagination; nothing else is wasted.

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?

For a read-only list tool there is no output schema, so the description carries the burden of describing return values, which it does not do at all. It covers scope and filtering adequately but omits result shape and the undocumented label_selector, leaving real gaps for an agent trying to interpret results.

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 50%: zone and label_selector are documented in the schema, while name and type are not. The description partially compensates by stating that name and type are filters usable independently or together ('and/or'), which is meaningful semantics the schema alone does not convey, though it still leaves match behavior (exact vs. substring) unstated and never mentions label_selector.

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 gives a specific verb and resource ('List record sets (RRSets) in a zone') with clear scope, and it identifies the zone as the container so an agent won't confuse it with the many other list_* siblings. It does not distinguish itself from the related write tool add_rrset_records or mention where it sits relative to any search variant.

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 only implied: the agent can infer this is the tool for inspecting DNS records in a zone, and the phrase 'filter by name and/or type' hints at narrowing. There is no explicit when-to-use versus when-not, no mention of prerequisites or scoping to a single zone, and no routing to an alternative.

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