Polymarket Agent Mcp

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: it manages live WebSocket connections (implying persistent state), streams real-time updates (continuous data flow), and allows connection status checking. However, it doesn't mention authentication requirements, rate limits, error conditions, or what happens when subscriptions exceed limits.

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 perfectly front-loaded with the primary purpose in the first clause, followed by specific action explanations. Every sentence earns its place by clarifying different aspects of the tool's functionality without any redundant or vague language.

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 no annotations and no output schema, the description provides adequate basics but lacks completeness for a WebSocket management tool. It covers the what and why of actions but doesn't describe return values, error responses, connection lifecycle details, or how streaming data is delivered to the agent.

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?

With 100% schema description coverage, the baseline is 3. The description adds meaningful context by explaining the overall purpose of managing subscriptions and connecting parameter actions to real-world outcomes (start/stop streaming, check connection). It doesn't provide additional syntax or format details beyond the schema, but enhances understanding of why parameters matter.

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 clearly states the tool's purpose with specific verbs (manage, subscribe, unsubscribe, check) and resources (WebSocket price subscriptions, real-time market updates, token_id). It distinguishes itself from sibling tools like markets.price (likely historical) and markets.watch (likely different functionality) by emphasizing live streaming and connection management.

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?

The description provides clear context for when to use each action (subscribe to start streaming, unsubscribe to stop, status to check connection), but doesn't explicitly state when NOT to use it or name specific alternatives. It implies usage scenarios without contrasting with other tools like markets.price or markets.events.

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