Get analytics

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

Annotations already mark this read-only and non-destructive; the description adds the concrete return shape (total posts, status breakdown, per-platform stats, daily counts), which is useful because there is no output schema. No hidden side effects or performance caveats are disclosed, but none are strongly expected for a read-only analytics summary.

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 with no filler; the action and scope are stated first, then the return payload and usage context. Every sentence earns its place.

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 simple read-only tool with two documented params, the description covers what it returns and when to use it. It could be more complete by distinguishing from get_post_metrics or view_analytics, but nothing required for a correct call 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 covers both parameters 100%, and the description only restates that it is a date range. The schema's ISO format examples carry the semantic weight, so the description adds no parameter-level detail beyond the baseline.

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?

Names a specific resource ('analytics summary') and scope (date range, overall across channels) with an explicit verb. It does not name or contrast siblings such as get_post_metrics or view_analytics, so differentiation relies on the 'overall' phrasing.

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?

Gives a clear trigger condition: when the user asks about overall content performance across channels over a date range. It does not state exclusions or explicitly name alternatives, but the intended context is unambiguous.

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