polymarket-trader-mcp

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

With no annotations provided, description carries full behavioral burden. It discloses the return value ('Returns the number of cancelled orders'), environment restriction ('live mode'), and licensing requirement ('Pro feature'). Lacks detail on irreversibility or partial failure modes, but covers the essential behavioral constraints.

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?

Five compact sentences with zero waste. Front-loaded with action and scope. Each sentence earns its place: scope (orders), platform (Polymarket), constraint (live mode), return value (count), parameters (none), and feature tier (Pro).

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?

Appropriately complete for a zero-parameter tool. Documents return value despite missing output schema. Could be improved by noting behavior when no orders exist (returns 0 vs error), but covers the critical operational constraints adequately.

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?

Zero parameters present per schema (empty object). Baseline 4 applies as per instructions. Description adds value by explicitly confirming 'No parameters needed', preventing the agent from hallucinating filter parameters that might exist in sibling tools.

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?

Description provides specific verb (Cancel), clear resource scope (all open/pending limit orders on Polymarket), and distinguishes from siblings like get_open_orders (read-only listing) and close_position (positions vs orders). The 'all' qualifier clearly signals bulk operation.

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?

Provides explicit constraints: 'Only works in live mode' establishes when-not to use (avoid in paper trading), and 'Pro feature' indicates access tier. No explicit comparison to hypothetical single-order cancellation alternatives, but 'No parameters needed' signals this is a nuclear option vs surgical tools.

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