polymarket-trader-mcp

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

No annotations provided, so description carries full burden. It identifies the operation as a simulation (implying read-only safety) and notes 'Pro feature' for access gating. However, missing: execution time expectations, rate limiting, whether results are cached, and specific return format details (no output schema exists to compensate).

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?

Four dense sentences with zero waste. Lead sentence establishes purpose, followed by user-value proposition, usage timing, and access tier. Every sentence earns its place; no redundancy despite descriptive richness.

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?

Adequate for a 2-parameter simulation tool without output schema. Covers input purpose (address + copy_budget), business logic (simulation), and user intent (validation). Minor gap: lacks explicit description of return structure (e.g., 'returns P&L summary and trade log') which would help given no output schema exists.

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 only 50% (address undescribed). Description compensates by identifying address as a 'wallet' via 'copy-traded this wallet.' Reinforces copy_budget semantics by referencing the $5 default implicitly through use case context. Could explicitly state address format expectations (e.g., Ethereum address).

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?

Excellent specificity: verb 'Simulate copying' + resource 'trader's historical trades' + outcome 'hypothetical P&L.' Clearly distinguishes from sibling analyze_trader by focusing on backtesting rather than current analysis, and references 'wallet' clarifying the address parameter target.

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 temporal guidance ('Use before adding a trader to your watchlist') and purpose ('validate their performance'). Also notes 'Pro feature' indicating access constraints. Lacks explicit 'when not to use' or direct comparison to alternatives like analyze_trader or score_trader.

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