Queryanalytics

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

No annotations are provided, so the description carries the full behavioral burden and discloses nothing: not pagination behavior despite cursor/limit parameters, not default time windows, not rate limits, not whether results are aggregated or raw. For a 15-parameter read tool with zero annotation coverage this is a serious gap.

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?

It is a single short sentence with no padding, but at this level of complexity brevity is under-specification rather than conciseness. Nothing is front-loaded beyond the bare verb and resource.

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?

Although an output schema exists and need not be described, the input side is completely undocumented: 15 parameters, an 11-value metric enum, and no annotations. An agent cannot determine valid filter combinations, time-range semantics, or pagination from this description.

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 0% across 15 parameters, and the description adds no parameter meaning at all. Ambiguous fields such as metric, series, partials, alignment, interval, destination_type, and the from_time/to_time dual string-or-integer types are left entirely unexplained.

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 names a specific verb ('Query') and resource ('NextDNS analytics metrics'), so the general purpose is graspable. It does not distinguish itself from the sibling plotAnalytics, which also operates on analytics data, leaving the boundary between 'query' and 'plot' to inference.

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?

There is no guidance on when to use this versus plotAnalytics, no prerequisites (e.g. needing a profile_id), and no mention of what to do when no time range is supplied. The single sentence implies only that it is for analytics retrieval.

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