top_movers

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

The description offers no behavioral details beyond the name. No annotations are provided, so the description carries full responsibility but fails to disclose core traits (e.g., read-only, sorting order, authentication needs, or whether it returns absolute or percentage changes).

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 extremely concise (single phrase), which is efficient but at the cost of adequacy. It is front-loaded but sacrifices completeness for brevity.

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 tool with no output schema and minimal parameter information, the description should hint at return format or interpretation (e.g., 'top movers by percentage change'). The current description leaves ambiguity about what 'biggest price movers' means, making it incomplete for practical agent use.

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?

Both parameters ('limit', 'period') are fully described in the input schema (100% coverage). The description adds no additional semantics beyond what the schema provides, meeting the baseline expectation.

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 'Biggest price movers on Polymarket' conveys a clear resource (price movers) and context (Polymarket), but lacks an explicit verb like 'list' or 'get'. It effectively distinguishes from siblings like 'top_markets' which deals with overall market rankings.

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?

No guidance is provided on when to use this tool versus alternatives such as 'detect_volume_spikes'. There are no examples, when-not-to-use conditions, or mentions of prerequisites.

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