getPredictionPayTokenList

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

Annotations already mark this as read-only and open-world, and the description adds useful context: Phase 1 supports only USDC, the endpoint returns USDC token info, and the returned token code should be used in the payTokenCode field of buy requests. No annotation contradiction exists.

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 understandable but redundant: 'Agent should call this before executing a trade' and 'Agent hint: Use this endpoint before placing a prediction market buy order' say the same thing, and 'Returns USDC token info' appears twice. Tighter editing would improve it.

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 zero-parameter read-only query tool with no output schema, the description is sufficiently complete: it names the returned fields, the supported token, and the intended pre-trade usage. It does not over-explain return structure, which is acceptable given the tool's low 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?

The tool has zero parameters and schema coverage is effectively complete, so the baseline is high. The description adds downstream semantic value by explaining how the returned token code maps to the payTokenCode field in buy requests.

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?

States a specific verb and resource: 'Query available payment tokens for prediction market trading.' It distinguishes itself from sibling tools like getPayTokenList by scoping to prediction markets, and explains what is returned: token symbol, code, and supported blockchain list.

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 clearly tells the agent when to call it: 'before executing a trade to verify supported payment tokens' and 'before placing a prediction market buy order.' It does not explicitly name alternative sibling tools or state when not to use them, so it stops short of full exclusion guidance.

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