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

Annotations indicate readOnlyHint=false, so the description's statement that it 'stores' a snapshot is consistent and adds a valuable nuance (point-in-time). However, it does not disclose potential side effects such as credit usage, latency, or whether the search is executed immediately. It adds some context beyond annotations but not rich behavioral detail.

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 a single sentence that is front-loaded with the core action and contains no filler. Every phrase adds value, making it concise and well-structured.

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?

The description explains the creation process and return type ('metadata'), but with no output schema, it leaves some gaps such as what the metadata includes or whether the operation is synchronous. The schema covers the input complexly, but the description could be more complete regarding response shape and potential limitations.

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?

The schema covers 100% of parameters with descriptions, so the baseline is 3. The description does not add additional parameter-specific meaning beyond what the schema already provides, and the schema descriptions are adequate for the parameters.

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 uses a specific verb ('Run'), identifies the resource ('LinkedIn Sales Navigator search'), and explains the key actions: storing a point-in-time contact snapshot and returning contact list metadata. This clearly distinguishes it from sibling tools like contact_lists-update or contact_lists-get.

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 does not provide any explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. While the name implies creation, the description simply states what it does and offers no context like 'use for creating new lists; use contact_lists-update for modifications.'

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