linkedin_compare_activity_periods

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the operation is read-only, whether it fetches new data or analyzes existing data, what permissions are required, or what the output structure looks like. The description focuses on purpose rather than 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, tight sentence that front-loads the core operation and then gives concrete output-oriented examples. Every phrase earns its place, with no redundant wording.

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?

With no output schema and no annotations, the description gives the conceptual outcome but omits practical details such as exact return format, data source, inclusivity of date boundaries, or limitations. It is sufficient for a high-level understanding but not fully complete for an agent needing precise invocation expectations.

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 100%, so parameter meaning is already fully documented in the input schema. The description adds the conceptual context of comparing two periods, but does not provide additional parameter-level semantics beyond 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 uses a specific verb ('compares') and resource ('activity across two date periods'), and immediately distinguishes this from single-period or timeline tools among the siblings by focusing on two-period comparison. It also states the analytical purpose: identify strategy shifts, new topics, or disappearing themes.

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 provides clear context for when to use the tool: when comparing activity between two periods to detect strategy shifts or thematic changes. It does not explicitly mention alternatives or exclusion conditions, but the use case is specific enough to guide selection among the many sibling tools.

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