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

Annotations already cover readOnly, idempotent, non-destructive, and openWorld. The description adds real value on top: it discloses the source platform (Polymarket), the derived metric (skill-weighted money vs. market odds) and its provenance (x402Pulse scoring), plus a non-advisory disclaimer.

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?

One dense but front-loaded sentence plus a short disclaimer; the core resource and payload are stated before the qualifying detail. Slightly heavy with stacked parentheticals, but nothing is wasted.

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-value explanation is unnecessary, and the description still characterizes the key field. It is complete for invocation; only the lack of routing guidance against sibling list/smart-money tools keeps it from a 5.

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% with a single 'limit' parameter ('1 to 10'), so the schema does the documenting work. The description contributes no additional parameter semantics, which is the correct baseline when coverage is high.

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 names a specific resource (busy Polymarket prediction markets about oil prices, OPEC, Strait of Hormuz, fuel) and the distinctive payload (skill-weighted money lean from x402Pulse scoring). This domain framing clearly separates it from siblings like list_attention_markets, get_oil_prices, and get_smart_money.

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?

Scope implies usage (query when oil-related prediction-market sentiment is wanted) and the 'busy' qualifier hints at a filtered subset, but no explicit when-to-use or alternative routing (e.g., vs list_attention_markets or get_oil_prices) is given. Only the 'Data, not trading advice' caveat sets any boundary.

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