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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: results are per-day series aligned to a shared `dates` array rather than totals, and scope is by LinkedIn account not campaign. It does not discuss pagination or limits, keeping it just short of 5.

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?

Front-loads the core definition and metric list, then routes to alternatives. The long metric enumeration is dense but informative; slightly verbose but every clause carries meaning.

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?

No output schema exists, but the description explains the return shape (per-day series aligned to a `dates` array) and the scoping dimension, which is the key thing an agent needs. Minor gaps around pagination/limits keep it from 5.

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 all four parameters (range, filter, userId, linkedAccountId) are already documented in the schema. The description adds only the `dates` alignment concept and the account-vs-campaign scoping note, not parameter syntax or format detail. Baseline 3 is appropriate.

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+resource (parallel daily series report) and enumerates the metrics returned, plus explicitly names the two sibling tools it is not (analytics_campaign, analytics_trend). An agent can distinguish it from siblings without opening any schema.

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?

Gives an explicit use case ("how did we trend over the last 30 days") and names alternatives with the conditions that select them: totals per campaign → analytics_campaign, months rather than days → analytics_trend. Also states the scoping caveat (LinkedIn account, not campaign).

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