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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered elsewhere. The description adds useful behavioral context by implying a time-series/comparative-over-time result and listing which metrics are observed, but it says nothing about granularity (daily points?), how the comparison baseline is computed, or account-resolution requirements.

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?

Two sentences, zero filler: the capability statement comes first, then the usage triggers. Every sentence earns its place and there is no restating of the name or title.

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 3-parameter read-only tool with full schema coverage and no output schema, the description covers purpose, metrics, and invocation context adequately. The remaining gap is the shape of the returned trend (period comparison vs. raw time series), which matters for how an agent reports results.

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% and the period enum (7d/30d/90d) is fully documented in the schema, so the baseline is 3. The description adds no parameter-level meaning beyond the schema — it doesn't explain the interaction between 'period' and the trend, or note that post_id accepts a shortcode as well as an ID.

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 ('Track'), a specific resource scope ('a specific post'), and enumerates the metrics tracked (reach, views, saves, shares) plus the temporal dimension. It implicitly separates itself from list-level siblings like get_top_posts or get_content_breakdown by scoping to one post, but it never names those siblings explicitly.

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 gives three concrete trigger scenarios: performance trend questions, 'still gaining traction' checks, and lifecycle analysis. That is clear when-to-use guidance, but there are no exclusions or named alternatives (e.g., use get_top_posts for ranking many posts), so the routing logic is only half-specified.

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