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

Beyond the readOnly/openWorld annotations, it discloses that the work runs server-side, that a costly or background run replies with a price first, the exact credit cost per platform and scale, that `handle` re-reads an earlier result for free, and how to recover from errors. This is unusually rich behavioral context for a tool with real cost attached.

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?

It is front-loaded with the purpose, followed by the billing table and the operating rules; every line carries information. The multi-line credit table is bulky but high-density, and it is arguably the most decision-relevant content for an agent weighing cost.

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 7-parameter, paid, possibly asynchronous tool with no output schema, this covers cost, confirmation, caching, and error handling well and sketches the return content. The notable omission is where it sits relative to sibling comment tools, and how paging or partial platform failures appear in the answer.

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 already 100%, but the description adds semantics the schema cannot: the per-platform credit cost for each scale tier, 'pass links whole, as given' for `targets`, and how `confirm`/`max_cost_credits` intersect with the price-quote flow. That goes beyond restating the fields.

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 states a specific output: topics with their shares, questions, buying intent, and complaints with quoted comments, under a given set of posts. An agent can tell what it produces. It stops short of naming how it differs from the sibling tools `comments` or `brand_buzz`, so the boundary is left to inference.

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?

Usage is only implied: you use it to learn what is being discussed under posts. Operational guidance is strong (pass links whole, run on error.fix, tell billing.display), but there are no exclusions or 'use X instead' routing against `comments`, `brand_buzz`, or `user_posts`.

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