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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description reinforces this with "Free and read only," which is a slight restatement rather than new information. It does add genuine behavioral context beyond the annotations: the scope of the data ("posts RipClip published or planned") and the fact that the comparison period is derived from the same window length. It stops short of noting latency, cost, or freshness of the underlying stats.

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 trigger phrases are front-loaded, and the "Not for" and "Next" segments give the paragraph clear scannable structure. It is on the long side, and the inline "timezone: IANA name, e.g. America/Chicago" is awkwardly embedded mid-list rather than grouped with the other parameter detail, but no sentence is wasted.

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 does not need to carry return-value documentation — yet it still summarizes the report contents, which helps an agent decide whether to call it at all. For a zero-required-parameter read tool, nothing needed to call it correctly 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 description coverage is 0%, so the description carries the full burden, and it does define both parameters: `days` sets the lookback window (default 7) and also implies the comparison window is the preceding equal-length period; `timezone` is specified as an IANA name with a concrete example (America/Chicago). It omits bounds or valid ranges for `days`, which keeps it from a 5.

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 opens with a concrete trigger ("a recap of how their posts did and what to post next") plus verbatim user utterances, and then enumerates exactly what the report contains: posts and views by platform, top posts at 24 hours, prior-period comparison, best time to post, and post_next clips. That is specific enough to distinguish it from every analytics sibling.

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 explicit when-to-use phrasing, an explicit "Not for" list naming four alternatives (get_post_stats, compare_platforms, show_report, why_it_worked) with the condition that selects each, and a follow-up route ("Next: plan_posts drafts the post_next clips"). Routing is fully disambiguated.

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