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

The description goes beyond the readOnly annotation by explaining data freshness (last 180 days, refresh every few hours), behavior for unsupported platforms, and the LinkedIn platform restriction. It also notes that metrics no platform reports are null, providing clear behavioral expectations.

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 detailed but every sentence carries useful information. It front-loads the core purpose, then covers output shape, usage guidance, platform behavior, freshness, and sibling tools without unnecessary 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?

Given the output schema is present and the input schema is fully described, the description provides complete context: what metrics are returned, how the comparison window works, platform restrictions, data freshness, and when to use alternative tools. No important caller-relevant behavior 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 descriptions already cover from, to, and platforms, but the tool description adds key semantics: metrics are based on posts published between from and to, the comparison window is the same length immediately before from, and omitting platforms means all platforms with analytics. This adds meaningful context 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 clearly states the tool returns workspace-wide performance metrics for a date window, including specific metrics and comparison values. It distinguishes itself from related analytics tools by naming get_analytics_timeseries, get_platform_breakdown, and list_post_analytics as alternatives.

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 explicitly says to use this for 'how did we do this month' questions and follower counts. It also provides guidance on when to call trigger_analytics_sync first and names alternative tools for trends, platform breakdowns, and individual post analytics.

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