Most active markets

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: ranking is by 24h volume and the results are limited to currently open markets across two venues. It omits pagination/truncation behavior and what happens when limit is omitted, so it adds value but not richly.

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 sentence, zero waste, and the ranking criterion and data scope are front-loaded. Nothing in it is padding or repetition of the tool name.

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 only two optional params, no output schema and annotations covering safety, the description is close to sufficient. Still missing: default limit value, what fields each market entry contains, and how ties or fewer-than-limit results are handled. Adequate but with clear gaps for a ranked-list tool.

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 50%: venue is documented only as 'default both' and limit has no description at all. The description partially compensates by naming the two venues and implying a volume-ranked ordered list where limit selects the count, but it never states a default limit or that the max is 25. Baseline 3 is appropriate given mixed coverage.

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 resource and ranking criterion ('top open markets by 24h volume') plus the venue scope ('Polymarket, Kalshi or both'). That is far more precise than the vague title 'Most active markets'. It does not explicitly name how it differs from siblings like search_markets, but the ranking/volume framing makes the distinction fairly inferable.

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?

The description says what the tool returns but never says when to reach for it instead of search_markets, get_market_odds, compare_markets or market_briefing. There are no exclusions, no prerequisites, and no mention of the default venue behavior driving selection. Usage is only implied by the word 'top'.

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