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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful non-schema context: the output is an interactive dashboard, the agent should summarise findings, and amounts are in the account currency. It does not mention rate limits, latency, or how missing data is handled, so it is helpful but not rich.

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 metric list is dense but front-loaded and immediately tells the agent what the dashboard contains. The trailing sentences about dashboard form, summarisation, default period and currency are each short and functional, though the long enumeration of metrics could be compressed slightly.

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 read-only, zero-required-parameter analytics tool with full schema coverage and no output schema, the description covers what is returned, how it is presented, the default time window, currency handling and the expected agent behaviour. Nothing an agent needs to invoke it correctly appears to be 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 every parameter is already documented, including the detail=summary vs full trade-off and the campaign/campaign_group levels. The description reinforces the default period and currency but adds no syntax or format detail beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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-and-resource pair (LinkedIn Ads performance dashboard) and enumerates the exact metrics delivered: spend, One Click Leads, website conversions, cost per result, clicks, CTR, CPC, CPM, leads, lead-form completion rate and conversion value. It also states the output structure (daily trend, per-campaign table, automatic insights), which distinguishes it from siblings like linkedin_ads or linkedin_breakdown that serve different purposes.

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?

It says to summarise the main findings and gives a default of last 30 days, which implies a reporting/analysis use case. However, it never states when to use this tool versus linkedin_breakdown, linkedin_campaigns, linkedin_conversions or the other platform performance tools (meta_performance, google_ads_performance, tiktok_performance), so the agent must infer the boundary itself.

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