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

With no annotations, the description carries the full disclosure burden. "Returns" implies a safe read and the threshold filtering behavior is stated, but the meaning of "recent" is undefined, and there is no mention of auth, rate limits, result ordering, or pagination behavior. It establishes the read-only nature but leaves several behavioral traits unstated.

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?

Two short sentences, zero filler, with the core operation and the filtering constraint front-loaded before the use-case hint. Nothing restates the tool name gratuitously.

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 simple read-only list tool with fully documented parameters this is close to adequate, but with no output schema the description never indicates what a trade record contains, and the undefined recency window is a real gap for correct invocation.

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%, so defaults and limits for limit, market_slug, and min_size_usd are already documented in the schema. The description only echoes the size-threshold concept behind min_size_usd without adding syntax or interaction details, so the schema does the real work.

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 verb and resource — returns recent large Polymarket trades filtered by a USD size threshold — which is concrete and distinguishable from siblings like get_trader_activity or get_wallet_transfers. It does not explicitly name which sibling to prefer for narrower queries, so it stops short of 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?

"Useful for detecting whale activity and smart-money flow" implies the use case but gives no explicit when-to-use/when-not guidance and never names alternatives (e.g., use get_trader_activity for a single wallet). The agent must infer the boundary from sibling names alone.

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