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

Beyond the readOnlyHint=false/openWorldHint=true annotations, it discloses the entire async contract: the call queues a cloud-browser workflow, returns {status, pendingReason, workflowId, operationName, message}, success carries no result data, and it enumerates error codes including interfaceLanguageNotSupported and noSalesNavigator. It even explains the two pendingReason values and the operational consequence of 'outsideWorkingHours' (report to user, don't loop). This is unusually rich behavioral disclosure.

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?

Purpose and effect are front-loaded in the first sentence, and the workflow/error detail follows in a logical order. The workflow paragraphs are generic boilerplate shared across linked tools and are somewhat heavy for a single-parameter delete, but they carry actionable guidance rather than filler.

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?

With no output schema, the description carries the return-shape burden and does so explicitly — a workflow acknowledgement with no result data, plus the exact follow-up call needed for the final outcome. Error taxonomy and pending-state semantics round out everything an agent needs to invoke and interpret this tool.

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?

Only one parameter exists and its schema description already covers 100% of the surface, so the baseline is 3. The description reinforces that listId is a string and that members remain saved, but adds no format, sourcing, or validation detail beyond what the schema states.

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 and resource ("Delete one owned list by string listId") and immediately scopes the blast radius ("keeping members saved and in their other lists"), which is exactly the distinction an agent needs from sibling mutations like nv_remove_lead_from_list or nv_rename_list. The "Plus-only root action nv.deleteList" tag also ties it to the underlying action namespace.

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 operating context — retrieve results via get_workflow_result with operationName nvDeleteList, and "Do not retry the original tool while a workflow is still running." It also states which inputs fail (unknown/shared/already-deleted → listNotFound, system lists → listNotDeletable). It stops short of naming an alternative for partial removals (e.g., nv_remove_lead_from_list) when the user only wants to shrink a list rather than delete it.

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