polymarket-trader-mcp

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

With zero annotations, carries full disclosure burden effectively. Explicitly states 'Read-only' and 'does not place trades' (safety-critical). Discloses return value ('score with detailed reasoning') and analysis factors. Missing minor details like data latency or caching.

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?

Three efficient sentences: methodology/output, safety constraint. Zero redundancy. Critical information front-loaded. Every sentence earns its place.

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 single-parameter tool with no output schema, description adequately compensates by describing return values (score, reasoning) and read-only safety. Sufficient given tool complexity.

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% for the single parameter (condition_id). Description mentions 'Polymarket market' which aligns with but does not significantly expand upon the schema's definition. Baseline 3 appropriate when schema documentation is complete.

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?

Specific verb 'Generate' + resource 'Polymarket market' + distinct output format 'BUY/SELL/HOLD recommendation'. Methodology (price, spread, trend, liquidity) clearly differentiates from execution siblings (buy, sell) and other analysis tools (check_market, assess_risk).

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?

Explicit exclusion 'does not place trades' clearly distinguishes from execution siblings (buy, sell, batch_order). 'Read-only analysis' clarifies safe, pre-trade usage. Lacks explicit positive guidance (e.g., 'use before trading') or comparison to analyze_trader.

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