Managelists

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

With no annotations, the description carries the full burden of behavioral disclosure, yet it provides none. It does not mention that operations like remove and replace are destructive, what permissions are required, whether changes are reversible, or how the profile state is affected. The word 'manage' weakly implies mutation but adds no real transparency.

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 front-loaded sentence with no wasted words. Its conciseness is efficient, but the extremely sparse content leaves the definition under-specified rather than optimally focused.

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?

An output schema exists, so return values need not be explained, but this is a 6-parameter, multi-operation mutation tool with no annotations and 0% schema description coverage. The description does not come close to covering the operational and parameter complexity an agent needs 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?

The schema has 6 parameters with 0% description coverage, and the tool description mentions none of them—not list_type, operation, profile_id, entry, entries, or entry_id. The presence of enums for list_type and operation helps the schema, but the description adds no semantic meaning beyond what is structurally encoded.

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 resource domain (allow/deny/block lists for a NextDNS profile) and implicitly distinguishes itself from siblings like manageProfiles and manageSettings. However, the verb 'manage' is broad and does not specify the supported operations (get/add/replace/update/remove) defined in the schema. An agent knows the general area but not the tool's actual capabilities.

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 tool versus alternatives such as manageRewrites or manageSettings, nor any prerequisites or exclusions. The description only states the domain, leaving the agent to infer usage context entirely.

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