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

Annotations only declare openWorldHint and non-idempotency, which is thin. The description adds genuinely behavioral facts the annotations do not carry: the tool is paywalled, and the pricing sibling must be consulted. It does not state rate limits, latency, or freshness guarantees beyond "right now".

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, no filler. The cost/paywall notice is front-loaded before the content description, which is exactly the order an agent needs to decide whether it can afford to call it.

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?

An output schema exists, so return shape need not be explained, yet the description still previews the key fields. Cost, scope, and count are all covered; only the ranking criterion for "most discussed" and data staleness are left implicit.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline for a 0-param tool is 4. Schema coverage is 100% and the schema is empty, so no gap exists.

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 precise verb+resource+scope: the three Polymarket/Kalshi markets most discussed on X right now, plus the payload (sentiment score, catalyst, volume trend). An agent can distinguish this from get_market_sentiment or get_market_brief purely from the description.

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?

It names a prerequisite and routes to a sibling ("Paid (see get_pricing)"), which is real usage guidance. However, it never says when to prefer this over the other market-oriented siblings (get_market_sentiment, get_market_brief, get_daily_scores), so selection still requires inference.

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