getPredictionTokenPrice

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

Without annotations, the description carries the full burden and explains the probability interpretation (0-1), the limit of 20 tokenIds, and the data returned. However, it omits potential behavioral details like authentication requirements or rate limits, leaving some room for improvement.

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 well-structured and front-loaded with key information. However, it contains some redundancy in explaining the price probability twice, making it slightly less concise than optimal.

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?

Despite no output schema, the description thoroughly explains the return values (best bid, best ask, last trade) and the probability meaning. It also includes usage hints and a sibling distinction, making it complete for a simple query tool with one parameter.

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 0%, so description must add meaning. It explains that tokenIds specify the tokens to query, imposes a maximum of 20, and implies they are string IDs. It adds value beyond the empty schema but does not detail the format of tokenIds.

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 current market prices for prediction outcome tokens, specifies the returned fields (best bid, best ask, last trade), and distinguishes itself from getPredictionPriceHistory by explicitly excluding price history queries.

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 explicit usage guidelines: call before placing orders, check price before buy/sell, maximum 20 tokenIds per request, and includes a clear directive to not use for price history, referencing the alternative tool getPredictionPriceHistory.

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