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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds provenance (Wikipedia input, Polymarket universe, x402Pulse scoring) and a "not investment advice" disclaimer, which is useful framing. It does not disclose pagination, freshness, or rate behavior, so it remains a modest add over the annotations.

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?

Front-loads the composite value proposition, then a usage line, then a disclaimer. Mostly efficient, though "Find markets the public is suddenly paying attention to" partially repeats the opening sentence and the framing borders on marketing prose. Generally tight and well-ordered.

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 detail is not the description's burden, and the two optional params are fully documented in the schema. The description covers what the tool returns conceptually and its data sources. The remaining gap is routing against near-duplicate siblings, which prevents 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% (both lang and limit documented, including the 1-10 range), so the schema does the heavy lifting. The description says nothing about either parameter, adding no meaning beyond structured fields. Baseline 3 applies when the schema fully documents parameters.

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 composite resource: Wikipedia trending/spiking topics joined to open Polymarket markets, with prices and a skilled-trader lean. The verb (list) and the intersection it covers are clear enough to distinguish it from adjacent siblings like list_trending_topics or get_topic_attention. It stops short of explicitly naming which sibling to prefer when, so it is not a 5.

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" implies a usage scenario, which is better than nothing. However, with many closely related siblings (list_attention_spikes, get_topic_attention, list_trending_topics, find_market_disagreements) there is no explicit when-to-use, when-not-to-use, or alternative routing. Usage is implied rather than stated.

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