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

With no annotations, the description carries the full behavioral burden. It does useful work by disclosing the payload shape ('each with prices and the skilled-trader lean from x402Pulse scoring') and a disclaimer framing, which is more than most. It is silent on freshness/caching of attention signals, whether results are ranked or capped, and any rate or authentication constraints — material gaps for a time-sensitive market tool.

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?

Three short sentences, front-loaded with the core concept before the use-case framing and the disclaimer. Little waste, though 'Attention meets prediction markets' is mildly promotional framing rather than informative content.

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 two-parameter, no-annotation, no-output-schema tool, the description adequately conveys what comes back and what it is for. But it leaves the `lang` parameter's meaning entirely unexplained and says nothing about recency of the attention signals, which is the central value proposition an agent must trust.

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 only 50%, and the description adds nothing to close the gap: `lang` has no schema description and no explanation in prose, leaving unclear whether it selects the Wikipedia language, a locale, or the market language. `limit` is already documented in-schema as '1 to 10' and the description neither repeats nor clarifies it. No semantic value is added beyond the schema.

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, distinctive resource and operation: Wikipedia attention trends (trending or spiking topics) matched to open Polymarket markets, enriched with prices and a scoring-derived trader lean. That is far more than a restatement of the name. However, it never distinguishes itself from its closest siblings (attention_spikes, attention_topic, attention_trending), so an agent must infer the boundary rather than being told it.

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?

'Find markets the public is suddenly paying attention to' frames the intended use case, and 'Data, not investment advice' sets expectations about interpretation. But there is no explicit when-to-use versus when-not, no named alternative among the three sibling attention_* tools, and no stated prerequisites or locality constraints. Usage is implied rather than guided.

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