search_network_lists

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

No annotations provided, and description does not disclose side effects, safety (read-only implied but not stated), pagination, limits, or authentication requirements. The description solely explains functionality without behavioral context.

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 plus example questions. Efficient but example list could be shortened or integrated. No verbose repetition.

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 low complexity (2 optional params, output schema present), description is fairly complete. Explains resource purpose and provides examples. Lacks mention of default behavior or ordering, but acceptable.

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%, so baseline is 3. Description adds context about network lists (IPs, CIDRs, countries) but does not clarify search semantics (e.g., exact match vs. substring). No enrichment beyond 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?

Description clearly states verb 'search' and resource 'network lists', with examples covering both list-all and filter-by-type scenarios. Differentiates from sibling 'get_network_list' by implying search/filter vs. single retrieval.

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?

Example questions imply usage scenarios, but no explicit guidance on when to use this tool versus siblings like get_network_list or search_properties. Could be improved by contrasting with related tools.

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