Managelogs

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

With no annotations, the description carries the full burden and mostly meets it: it warns that clear deletes all stored logs, that download ignores time filters, and that raw bypasses dedup/noise filtering. It omits any permission/auth requirements and return-volume or pagination behavior for get.

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?

Front-loaded with the one-line purpose, then operations, then time semantics, then examples. Well-structured with no filler, though the four copy-paste examples are somewhat repetitive with the operation bullets above them.

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 multi-operation tool with an output schema present, the description covers operation semantics, filter interactions, and time formats adequately. The remaining gap is the unexplained user/device filters, which an agent would have to guess at.

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%, so the description must compensate. It explains operation, limit, raw, from_time and to_time meaningfully, but the user and device parameters are never mentioned, leaving two of eight parameters undocumented in both schema and description.

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 first line states the resource (query logs for a NextDNS profile) and the operation set (get/clear/download) is enumerated immediately after. 'Manage' alone is vague, but the bulleted operations make the tool's scope unambiguous and separable from siblings like queryAnalytics or manageProfiles.

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?

Each operation's purpose is spelled out, and the description explicitly says from_time/to_time are ignored by the download endpoint and only used by get, which prevents a common misuse. It stops short of saying when to prefer this over queryAnalytics for log retrieval, so no exclusions or named alternatives.

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