linkedin_analyze_prospect

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

With no annotations, the description must carry the behavioral disclosure burden, but it only says the tool 'orchestrates' several analyses. It does not state whether the operation is read-only, what side effects or dependencies exist, how output is returned, or whether it invokes the sibling tools.

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 tight sentence that front-loads the core identity ('High-level prospect analyzer') and then lists the orchestrated components. There is no filler or 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?

For a tool with 3 parameters, a nested object, no output schema, and 19 siblings, this description is under-specified. It fails to state required inputs, expected output, when to use it instead of lower-level alternatives, or any operational constraints, leaving important gaps for an agent.

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 only 33%, and the tool description does not compensate by explaining profileId, icp, or objective. The nested icp object has useful subproperty descriptions in the schema, but the main parameters' semantics remain underspecified and the description adds no parameter-level meaning.

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 ('analyzes') and resource ('prospect'), and explicitly frames the tool as a 'High-level' orchestrator combining profile, company, signals, ICP matching, and lead scoring. This clearly distinguishes it from focused siblings like linkedin_analyze_profile, linkedin_match_icp, and linkedin_score_lead.

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?

No guidance is provided about when to choose this orchestrator versus the individual sibling tools, nor are any alternatives or exclusions mentioned. The agent must infer from the word 'high-level' that this is a composite operation, which is not sufficient.

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