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

No annotations are provided, so the description carries the burden. It discloses that the tool returns aggregate data across all published posts and mentions the optional filters, but doesn't disclose details like whether it's read-only, rate limits, or what happens with no filters (defaults to last 30 days). The behavior is reasonably clear but not deeply transparent.

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 two sentences, front-loads the core purpose and metrics, and ends with concrete usage examples. It's efficient and well-structured, though the usage examples could be slightly more concise.

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 analytics tool with 3 optional parameters and no output schema, the description covers the main purpose, metrics, and filter options. It doesn't explain the default date range behavior or the exact response structure, but given the tool's simplicity and the presence of sibling tools for deeper analytics, it's reasonably complete.

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 0%, so the description must compensate. It explains startDate/endDate as date range filter (YYYY-MM-DD) and platform as a filter, which adds meaning beyond the raw schema. However, it doesn't clarify whether both dates are required together, what the default range is, or the exact effect of each parameter beyond 'filter'.

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 fetches aggregate analytics across all published posts, listing specific metrics (total impressions, engagement, post count, per-platform breakdown, last 30 days timeline). It distinguishes itself from sibling tools like get_post_analytics and get_content_insights by focusing on aggregate overview rather than individual post or content-level analytics.

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 explicitly provides usage examples ('how did my content perform last week?' / 'what's my engagement on Instagram?') and states the optional filters (date range, platform). This gives clear guidance on when to use this tool versus alternatives, though it doesn't explicitly name sibling alternatives.

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