linkedin_find_opportunities

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 only states that the tool identifies opportunities from activity, but does not disclose what input is used (beyond a generic profileId), whether it performs analysis, what side effects exist, or what the output looks like. This is minimal and leaves the agent guessing about the tool's behavior.

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 wasted words and fronts the verb immediately. However, it is terse to the point of omitting important context, so brevity is achieved at the expense of usefulness rather than through efficient structure.

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?

There is no output schema, no annotations, and no mention of return values or expected behavior. The description does not explain what a caller should expect after invocation, what 'opportunities' means in practice, or how the profileId and category parameters influence results. For a 2-parameter tool, this is incomplete.

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 50%: profileId has a description, but category has none. The tool description adds no parameter meaning and does not explain what 'category' values are valid or how category affects opportunity identification. Since the description does not compensate for the under-documented parameter, this is a meaningful gap.

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 ('Identifies') and names a distinct resource ('specific technical tracking or marketing service opportunities') with a stated basis ('observed activity'). This clearly separates it from sibling tools like linkedin_rank_leads or linkedin_extract_topics, though the meaning of 'technical tracking or marketing service opportunities' is somewhat jargon-heavy.

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 'based on observed activity' implies the tool should be used when there is activity data to analyze, but it does not explicitly state when to use this tool versus alternatives like linkedin_detect_business_signals or linkedin_analyze_recent_activity. No exclusions or alternative routing are provided.

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