Get cached post analytics

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

Annotations already mark readOnlyHint=true and destructiveHint=false. Description adds critical behavioral details: no background refresh, captured_at meaning, no platform calls, exemption from live rate limit. No contradiction with annotations.

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?

Three sentences, each packed with distinct information. No redundancy. Front-loaded with the core caching purpose. Example of efficient writing that earns every word.

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 tool with 6 parameters, an output schema, and caching behavior, the description covers all essential aspects: data freshness, rate limit distinction, pagination, and platform filtering. Nothing missing for correct 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 covers 100% of parameters with descriptions, so baseline is 3. Description adds value by explaining pagination mechanism (cursor, has_more) and default behaviors (date range defaults). Does not repeat schema but enriches understanding.

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 clearly states it replays cached post metrics from Upload-Post, not fresh platform calls. It explicitly names the sibling tool `get_post_analytics` and differentiates by noting it only contains previously fetched posts. This makes the purpose unmistakable.

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?

Provides explicit guidance: prefer this tool when scanning many posts or paging through history. Contrasts with `get_post_analytics` regarding rate limits and live data. Tells when not to use (posts never queried live) and why (no background refresh).

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