linkedin_build_activity_timeline

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, yet it only states that a chronological summary is produced. It does not say whether the operation is read-only, what activity scope is covered, whether 'from' and 'to' bound the timeline, or what the returned summary contains — especially problematic given that no output schema exists.

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?

A single, front-loaded sentence with no filler — the verb and resource lead immediately, and every word earns its place. It is arguably under-specified, but that is a completeness concern rather than a conciseness defect.

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 and no output schema, the description should at least explain the inputs, the activity scope, and the shape of the returned summary; it explains none of these. At 3 parameters with 33% schema coverage, an agent can guess the basics but cannot confidently predict behavior or output.

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 coverage is only 33%, and the lone description ('Profile ID') is tautological, so the description needed to compensate but never mentions parameters. The words 'chronological' and 'timeline' weakly hint that 'from' and 'to' are date bounds, but this is never stated, and profileId semantics are left entirely to the schema.

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 action ('Constructs') and a concrete deliverable ('a chronological activity timeline summary'), so an agent can tell this assembles activity data into an ordered summary. However, it does not explicitly differentiate the tool from the activity-related siblings (e.g., linkedin_get_recent_activity, linkedin_analyze_recent_activity, linkedin_compare_activity_periods); the distinction rests only on the implicit word 'timeline.'

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 guidance, exclusions, or alternative routing is provided; the only hint is the bare function statement itself. With 19 siblings, including at least four activity-centric tools, an agent gets no help deciding between this tool and linkedin_get_recent_activity or linkedin_compare_activity_periods.

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