linkedin_research_profile

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It does describe an internal pipeline and the returned artifact ('actionable outreach angles'), which is useful. However, it does not disclose whether the operation is read-only, whether it has side effects, what data it relies on, how long it might take, or any auth/permission expectations. The high-level step list provides some transparency but not enough for a tool of this complexity.

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 with no filler words, and it front-loads the high-level purpose ('Runs full end-to-end profile research') before listing the component behaviors. The comma-separated list is slightly dense but every item conveys a distinct part of the tool's function. It is concise and readable, though not as tightly structured as a two-sentence version with explicit scoping.

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?

This is a complex tool with 5 parameters, a nested icp object, no output schema, and 19 sibling tools, but the description does not clarify output structure, prerequisite relationships, or how the optional parameters affect behavior. It does not explain what happens if icp is omitted despite being required for the claimed 'evaluates ICP match' step, nor does it describe the format of the returned outreach angles. The description is too thin for an agent to confidently invoke this tool in varied contexts.

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 60%, so the schema already documents most parameter meanings. The tool description adds little beyond the schema: it mentions ICP matching, which loosely aligns with the icp parameter, and 'activity normalization', which implies from/to date usage, but it does not clarify how parameters interact or what the objective field controls. The description mostly restates concepts already present in the schema rather than adding new semantic clarity.

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 states a specific verb ('Runs'), a clear resource ('full end-to-end profile research'), and enumerates the concrete sub-steps (normalizes activity, extracts topics, detects signals, evaluates ICP match, returns outreach angles). This clearly differentiates it from the many sibling point-tools like linkedin_extract_topics or linkedin_detect_business_signals, which each handle only one step.

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 implies usage for a complete profile research pipeline but gives no explicit guidance on when to choose this over the individual sibling tools. It does not state exclusions, alternatives, or conditions under which a more specialized tool would be preferable. The 'full end-to-end' phrasing hints at the use case but leaves the selection decision mostly to inference.

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