linkedin_analyze_search_results

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions categorizing, filtering, and preliminary scoring, but does not clarify whether filtering modifies the stored batch, whether any data is destroyed, how optional ICP affects behavior, or what the output format is. This is a significant transparency gap for a processing tool.

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 concise sentence with no wasted words. It front-loads the primary actions and clearly identifies the resource being operated on.

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 tool has a nested optional icp object and no output schema, meaning the description should explain what results are produced and whether the batch is mutated. It provides none of that. The description is also too sparse relative to the complexity of the operation and the number of sibling tools performing similar functions.

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 the schema already documents both parameters, including the nested icp properties and searchId meaning. The description adds minimal extra value by linking 'preliminary ICP scoring' to the icp parameter, but it does not need to compensate for schema gaps.

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 provides specific verbs and resources: 'Categorizes, filters, and performs preliminary ICP scoring on an imported search result batch.' This clearly states what the tool does. However, it does not explicitly differentiate itself from sibling tools like linkedin_filter_leads or linkedin_match_icp, relying on the word 'preliminary' to imply a distinction.

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 phrase 'imported search result batch' implies the tool should be used after an import and before more detailed scoring or ranking, giving some contextual guidance. However, there is no explicit guidance on when to use this tool versus alternatives such as linkedin_filter_leads, linkedin_match_icp, or linkedin_rank_leads, nor any exclusions.

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