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

readOnlyHint=true already declares the safety profile, so the description's job is to add context, and it does disclose two non-obvious traits: header lines reporting applied filters/defaults, and a <=4 KB result cap with paging. However, the phrasing is so compressed ('the rows line pages on') that the actual pagination/truncation semantics remain ambiguous, and nothing is said about defaults beyond 'what the defaults hid'.

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 dense sentence-fragments, front-loaded with the purpose, so nothing is obviously wasted. But the telegraphic style ('head lines say what applied and what the defaults hid', 'the rows line pages on') crosses from concise into cryptic and costs comprehension.

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?

Insufficient evidence to score; the description has no bearing on this dimension.

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 95%, so the baseline is 3, but the description genuinely adds meaning for three key filters: copyable ('% of checked trades a follower could fill', n=checked), ret_lo ('profit per copy as % of stake, 80% low end', n=kept_n), and crowd ('% copied within 2 s, upper bound'). These definitions go beyond the terse schema strings, though most of the 20 parameters receive no extra explanation.

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 opening noun phrase 'Polymarket traders, filtered and sorted like the page' conveys a filtered trader listing but never states a verb (list/find/search) or scope explicitly. It does not name or differentiate from siblings such as get_trader (single trader) or list_categories, so an agent must infer the distinction. Purpose is recognizable but not sharp.

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?

There is no when-to-use guidance, no prerequisite or exclusion, and no named alternative among the siblings. 'like the page' and the paging sentence hint at behavior but give no conditions for choosing this tool over get_trader or the recipe/bot guides.

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