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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new context: numbers come from a snapshot up to an hour old, frequent calls are free, Telegram exposes no analytics, and refresh is rate-limited (429 analytics_refresh_rate_limited with Retry-After). This is rich disclosure well beyond the 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?

Front-loads the purpose and platform list, then packs the caching and refresh behavior into a single efficient sentence. Slightly dense but no filler; every clause 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?

With no output schema, the description usefully names the returned metrics (likes, reposts, replies, etc.), covers platform support and the Telegram gap, and explains snapshot freshness and refresh. It does not describe the response shape in detail, but is otherwise complete for a two-parameter read tool.

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 schema already documents post_id and the full refresh rate-limit behavior. The description largely restates the snapshot/refresh tradeoff, adding little syntax or meaning the schema does not already carry, so the baseline 3 applies.

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?

States a specific verb and resource ('Get analytics (likes, reposts, replies, etc.) for a published post') and enumerates the supported platforms, so the agent knows exactly what is retrieved. It stops short of explicit sibling differentiation (e.g. vs chirpie_get_post), keeping it below a 5.

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 gives strong operational guidance for the refresh parameter ('calling this often costs nothing; set refresh to ask the platform now instead') and flags that Telegram is unsupported. However, it never states when to pick this over a sibling such as chirpie_get_post, so tool-selection guidance is only implied.

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