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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing snapshot freshness (refreshed at most every six hours), the meaning of the `stale` flag when LinkedIn rate-limits, null semantics for unreportable metrics, and which field lists refused metrics. This is exactly the operational context an agent needs to interpret results.

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?

Return contents are front-loaded and every clause carries information — metric list, day window, null/stale semantics. The multi-clause semicolon-joined sentences are dense and slightly hard to scan, but there is no filler.

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, the description shoulders the burden of explaining the response and does so: it names the metric families, explains null and unavailable entries, and describes the freshness/stale mechanism. Nothing an agent needs to call and interpret this tool is missing.

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 the schema already documents `days`, `accountId`, and `profileId`, including the accountId/profileId agreement rule. The description's only parameter-related content (1-30 days, default 28) restates the schema and adds nothing new, so baseline 3 applies.

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?

States a specific verb (Return) and resource (LinkedIn Page's or personal profile's insights) and enumerates exactly which metrics come back, including the Page-only extras (clicks, Page views). An agent can immediately tell this is account-level LinkedIn analytics rather than post-level (get_linkedin_post_insights) or another platform's metrics.

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 scope (account vs profile, 1-30 complete UTC days, default 28) implicitly frames when this tool applies, but there is no explicit routing guidance such as 'for post-level metrics use get_linkedin_post_insights' or prerequisites for obtaining an accountId. Usage is inferable rather than stated.

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