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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them: per-address quota of 3 quotes per 7 days, the quotes_left counter, the exact refusal payload (rate_limited with reason guest_quote_limit, retry_after, resets_at), and the fact that results are a timestamped range rather than a binding plan.

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 lead sentence ('No account needed.') is well front-loaded, but the second sentence is a dense run-on that stitches together output fields, multipliers, creator counts and read timestamps in one breath. Nearly every clause carries information, yet the packaging makes it harder to parse than a short bulleted structure would.

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 discloses the return contents (price range, creator count, read timestamp, quotes_left) and the error shape for rate limiting, which is exactly what the agent needs to interpret results. It stops short of stating currency/unit conventions or what the range bounds mean in practice.

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%, and the schema already documents both the 1-50 posts bound and the post/quote/thread enum meanings. The description restates 'the number of posts you name (1 to 50)' and the format concept without adding units, currency, or default behavior beyond the schema, 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 output (all-in price range a brand pays per post, in one format, across every creator on sale now) scaled by posts, and explicitly contrasts it with a real plan that names creators and dates. That contrast does the sibling-differentiation job conceptually, but it never references the actual sibling tools in this server (inventory, resolve_audience), so the agent must infer the boundary itself.

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?

Clearly says when this is appropriate (no account needed, guest path) and when it is not (a plan names creators and dates and needs an account, with 'claim' pointing to sign-in/key creation). The 3-quotes-per-7-days constraint and refusal condition are spelled out, though no sibling tool is named as the alternative for account holders.

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