get_analytics_summary

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

No annotations are provided, so the description carries the full burden. It discloses the kind of data returned and includes a caveat about platform-specific engagement fields, but it does not explicitly state side-effect status, data window boundaries, or any operational limitations beyond the input parameter.

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 entire meaning is packed into one efficient sentence with no filler. The parenthetical 'where each platform exposes them' earns its place by preventing an incorrect assumption about engagement metrics.

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 summary tool with one optional parameter and no output schema, the description covers the main return facets without requiring an output schema. It could be slightly more explicit about aggregation semantics, but nothing critical is missing for basic invocation.

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 `days` parameter is already documented with type, range, and default. The description adds only the phrase 'recent window,' which aligns with but does not enrich the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Get') and resource ('analytics summary') and enumerates the exact content: post counts, verified-live rate, per-platform breakdown, and engagement totals. This clearly distinguishes it from siblings like get_mentions and list_connected_accounts.

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 description implies when to use the tool—when an analytics summary is needed—but gives no explicit guidance about alternatives or when not to use it. Siblings like get_mentions and schedule_post exist, yet no routing or exclusion criteria are mentioned.

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