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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the refresh path re-reads the networks live, is throttled to at most once every ten minutes, and the default path serves already-collected data — useful context an agent would otherwise have to guess.

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, front-loaded with what is returned before the parameter guidance; each clause (history, growth use case, throttle, default) carries information the agent needs.

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 carries the return-value burden and does so by describing the shape of the result (latest plus historical readings per network). Minor gaps remain on error behavior for unpublished or deleted posts and on the time window of history, but the essentials are present.

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 coverage is 100%, so both parameters are documented structurally. The description still adds value by explaining the ten-minute throttle on refresh and contrasting it with the cached-read default, which goes beyond the schema's bare "Read the networks again now. Defaults to false."

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 resource (the performance numbers for one published post) and its scope: the latest reading plus every earlier one across all networks it was published to. That clearly separates it from get_post and get_post_status, though it never names those siblings explicitly.

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 use case ("so you can say whether it is still growing") and an explicit rule for when to enable refresh versus leave it off. It does not, however, exclude or route to the sibling tools like get_post or get_post_status.

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