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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world, so the safety profile is covered. The description adds genuine value by characterising the payload: cumulative totals per day and the day-over-day growth, which tells the agent the granularity and derivation of the returned data.

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?

A single dense sentence, front-loaded with the core action and resource, with the explanatory clause after the colon earning its place by clarifying the return shape. No waste.

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?

An output schema exists, so the description need not enumerate return fields, and it still sketches the structure (daily cumulative totals plus growth). For a one-parameter read with rich annotations, nothing essential is missing, though naming the sibling tools would round it out.

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 analytics_id's origin (from list_post_analytics or get_analytics_summary) is documented in the schema itself. The description adds no syntax or sourcing detail beyond it, so the baseline of 3 applies.

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 (Read) and resource (one post's lifetime metrics plus day-by-day history), and the phrase 'one post's' implicitly scopes it apart from list_post_analytics. It never names the sibling tools, so differentiation is available only by inference from the singular framing.

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 singular 'one post's ... history' implies this is the per-post detail tool versus a listing tool, but there is no explicit when-to-use, when-not, or named alternative. The reference to list_post_analytics and get_analytics_summary is only in the schema, not the description.

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