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

With no annotations, the description carries the full burden. It does add real behavioral value: metrics are relative to the user's own baseline, and every bucket carries a full metric breakdown. But it omits cost/latency implications, which matter given the presence of get_cost_estimate/get_credit_balance siblings and a preview_ variant that implies this is the expensive call.

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?

Front-loaded with the payoff (optimal posting patterns) and the four buckets, then the metric semantics, then the optional scope. Four sentences, all mostly earning their place; the scope sentence duplicates schema content, which is the only 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?

No output schema and no annotations, so the description must stand in for both. It does a fair job describing returned buckets and metric definitions, but leaves the default time window and any cost/side-effect profile unstated – a moderate gap for an analytics call that may consume credits.

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%, so the baseline is 3. The scope sentence restates the schema's meaning slightly more operationally ('recompute the patterns against a specific collection'), but date_from/date_to are ignored entirely – the description never says whether patterns default to all-time or a trailing window, which is the one genuinely ambiguous parameter behavior.

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?

Specific verb+resource plus an enumeration of what the response contains (best day, best hour, format breakdown, character-length sweet spot), which clearly separates it from generic siblings like get_profile_summary or get_engagement_trends. It never names the closest sibling, preview_posting_insights, which reads as the preview counterpart to this tool, so the differentiation is incomplete.

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?

Usage is only implied – the description says what patterns you get, not when to reach for this over preview_posting_insights, get_topic_insights, or get_engagement_trends. The one explicit conditional it does give is for `scope` (recompute against a specific collection), which is helpful but narrow.

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