linkedin_analyze_recent_activity

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

No annotations are provided, so the description carries the full disclosure burden. The word 'Analyzes' implies a non-mutating read operation, and listing three analysis dimensions adds real behavioral context. However, it never explicitly states that the tool is read-only, has no side effects, or requires any preconditions, leaving part of the safety profile implicit.

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?

One sentence, front-loaded with the verb and resource, with zero filler words. It is efficient, though arguably too terse given that no annotations or output schema exist to carry additional context — a few more sentences of guidance would have earned their place.

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 no annotations, no output schema, and 18 siblings with meaningful overlap, the description is too thin. It never clarifies how this tool differs from linkedin_extract_topics or linkedin_detect_business_signals, what objective controls, or what the returned analysis looks like.

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 25% (only profileId is described), so the description must compensate. The phrase 'date-range' gives semantic meaning to the to/from parameters, but it omits any format or boundary details, and the objective parameter is entirely unexplained despite having a default of 'prospect_research'. Compensation is partial at best.

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 names a specific verb ('Analyzes') and resource ('date-range activity'), and enumerates three concrete analysis outputs: recurring topics, priority shifts, and business signals. It overlaps somewhat with siblings like linkedin_extract_topics and linkedin_detect_business_signals, but the combined analytic scope is specific enough that an agent knows what the tool produces.

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 when-to-use or when-not-to-use guidance is provided, and no alternative tools are named. With 18 siblings including several that closely overlap (linkedin_get_recent_activity, linkedin_extract_topics, linkedin_detect_business_signals, linkedin_compare_activity_periods), an agent cannot reliably decide which tool to invoke.

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