Managelists

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

With no annotations, the description carries the full burden and does well: it discloses local validation behavior (entries lacking a string 'id' rejected with invalid_argument, named by index for replace), the destructive nature of 'replace' overwriting the entire list, and the list-type restriction on 'update'. It omits permission/auth requirements and any rate-limit or mutation-side-effect notes.

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 purpose, then cleanly sectioned into list types, operations, and examples, so it scans well. The six examples are largely a restatement of the operations section and add length, though each is individually compact and useful.

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 6-parameter, multi-operation tool with 0% schema coverage and no annotations, the description supplies everything needed to call it correctly: valid list types, per-operation argument shapes, validation failure modes, and an output schema covers return values. No meaningful gap remains.

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, and it does: 'entry' is documented as either {"id": "value"} or a plain id string, 'entries' as a list of dicts, 'entry_id' as the remove/update key, plus the accepted values for list_type and operation. The worked examples pin down exact call shapes for each operation.

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 opening states a specific verb and resource ('Manage allow/deny/block lists for a NextDNS profile') and then enumerates the exact list types and operations, which cleanly separates it from siblings like manageSettings, manageProfiles, and manageRewrites. An agent can identify what this tool covers without opening the schema.

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 is defined with its intended use ('get' returns, 'add' appends, 'remove' deletes, 'replace' overwrites the entire list), and a constraint is given for 'update' (only allowlist/denylist/parental_categories/parental_services). There is no explicit comparison against alternative tools for overlapping tasks, which keeps it short of a 5.

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