Browse List Pool

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

Annotations already provide readOnlyHint=true, so the safety profile is clear. The description adds that lists are 'verified' and supports filtering, but does not reveal additional behavioral traits beyond what's in the schema and annotations.

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?

Two sentences, very concise, front-loaded with the core action and scope. Every word adds value without redundancy.

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?

Given the simplicity of browsing with filters, the description is mostly complete. Lacks details about the return format, but for a read-only list operation, this is acceptable. Output schema is absent, so the agent must infer the structure.

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 100% with each parameter described in the input schema. The description only mentions filtering by category or region, adding no new meaning beyond the schema. Baseline of 3 is appropriate.

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?

Explicitly states the verb 'browse', the resource 'verified contact lists', and the context 'marketplace pool'. Clearly distinguishes from siblings like 'neuron_browse_pool' (general pool) and 'neuron_list_contact_lists' (user's own lists).

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?

Provides clear context for when to use: browsing marketplace contact lists. Implies filtering by category or region. Does not explicitly state when not to use or mention alternatives, but the purpose is well-defined enough to infer proper usage.

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