getPredictionPayTokenList

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

With no annotations, the description carries full burden. It discloses that the tool returns token symbol, code, and blockchain list, and mentions the Phase 1 limitation (USDC only). No side effects are expected for a read-only query.

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 contains some repetition, e.g., 'AI agent should call this before executing a trade' and 'Agent hint: Use this endpoint...'. It is clear but could be more concise by merging similar instructions.

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 output schema, the description adequately explains the return values (token symbol, code, blockchain list) and how to use the token code in buy requests. It covers the essential context for a simple query tool, though it does not mention pagination or error handling.

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?

The tool has no parameters (empty schema, 100% coverage), so the description does not need to add parameter details. The baseline for 0 parameters is 4, as the description adds value by explaining the output context, even though it doesn't describe parameters.

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 queries available payment tokens for prediction market trading, specifying that it returns token symbol, code, and supported blockchain list. It distinguishes from sibling tools like getPayTokenList by explicitly targeting prediction market, and notes Phase 1 supports USDC only.

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 advises the AI agent to call this before executing a trade to verify supported payment tokens, and provides a specific hint about using it before placing a prediction market buy order. While it doesn't explicitly exclude other contexts, the purpose is clear enough to guide appropriate use.

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