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

Annotations already establish that this is a read-only, open-world, idempotent, non-destructive operation. The description adds material behavior beyond that: Tier 1-3 trader filtering, coverage across every covered Polymarket question, access-tier differences in freshness and anonymity, and an explicit caution that the output is information rather than a signal.

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?

The description is front-loaded with the use case and then explains what is returned and how access tiers affect visibility. The closing past-performance disclaimer is generic boilerplate, but the overall structure remains clear and efficient.

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?

Given the zero-parameter schema, rich annotations, and existing output schema, the description supplies enough contextual detail for correct invocation. It covers the use case, data universe, trader tier filter, freshness, and access-tier limitations without needing to restate return values.

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?

The tool has zero parameters, so the rubric baseline is 4. The description does not add parameter-specific detail, which is appropriate because there is no input schema to clarify.

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 states that the tool surfaces the newest smart money moves across every covered Polymarket question, including whether a Tier 1-3 trader bought or sold an outcome and its current price. That is a specific resource and scope, though it does not explicitly contrast itself with close siblings such as kellian_get_smart_money.

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?

It opens with an explicit usage condition: use this when someone asks what is moving on prediction markets now. That gives clear invocation context, but it does not state when not to use it or name alternative tools for related questions.

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