Get DNS search filters

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

Annotations already establish read-only, idempotent behavior. The description adds useful non-obvious behavior: it does not return products and requires at least one of query/category. It does not disclose response shape or error conditions, but these are not critical given the annotations.

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?

Three tight sentences with no filler. The key scoping statement ('Does not return products') is placed early, and the usage constraint is front-loaded.

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?

Despite the simple surface, the description conflicts with the empty input schema: it demands a query/category argument the schema does not declare, so an agent cannot reliably construct a valid invocation. No output schema, pagination, or error behavior is described, which further reduces completeness.

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?

The input schema is empty, so the description is the only source of input semantics; mentioning 'query or category (one required)' adds meaning beyond the schema. However, it stops short of giving explicit parameter names or types, leaving some patchiness in how to actually invoke the tool.

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 exposes available filters and sort options for a search query or category, which is a specific resource distinct from product-returning search endpoints. 'Does not return products' actively differentiates it from sibling search tools.

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?

It gives clear context: use this for filter/sort metadata rather than products, and states that one of query or category is required. It does not explicitly name sibling alternatives, so agents must infer which sibling to use when products are needed.

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