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

Annotations already cover the read-only, idempotent, non-destructive nature of the tool. The description adds that the lists are verified and come from a shared marketplace pool, which is useful context. It does not disclose return format, pagination behavior, or next-step actions, but this is not critical given the annotation coverage.

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 two short, front-loaded sentences: the first states the core purpose, the second lists the primary filter dimensions. No filler or redundant wording is present.

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 read-only browsing tool with six optional parameters and no output schema, the description is workable but incomplete. It does not mention pagination, the smsEnabled curation use case, or how this differs from the generic neuron_browse_pool. The schema fills parameter gaps, but the description alone leaves some routing and return expectations to inference.

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 coverage is 100% and each parameter already has a meaningful description, including examples and a cross-reference to neuron_create_sms_campaign. The description merely summarizes filtering by category, region, or search term, adding no meaning beyond the schema.

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 states a specific verb ('Browse'), resource ('verified contact lists'), and location ('shared marketplace pool'), and mentions filtering dimensions. This makes the tool's purpose clear and distinguishes it from generic marketplace tools like neuron_browse_pool, though it does not explicitly name the sibling.

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?

The description gives a clear use context: browsing and filtering marketplace contact lists. However, it does not provide explicit guidance on when to use this tool versus related siblings such as neuron_get_pool_item, neuron_install_from_pool, or the more generic neuron_browse_pool.

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