get_prediction_markets

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

No annotations are provided. The description fails to disclose whether the tool is read-only, whether it aggregates data, or any side effects. It only lists three platforms without behavioral details.

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 extremely concise at 5 words, but this brevity sacrifices clarity and utility. It lacks a verb and front-loading of critical information. While it is not verbose, it is under-specified.

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?

Without annotations, output schema, or parameter explanations, the description is severely incomplete. It does not cover return value, behavior, or how to use the two parameters. The context signals indicate low schema coverage, and the description fails to compensate.

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 0% schema description coverage, the description must explain parameters but does not. It does not mention 'topic' (a keyword for filtering) or 'limit' (maximum results). The description adds no semantic value beyond the schema structure.

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 'Polymarket + Kalshi + Azuro odds.' is a noun phrase lacking a verb. It implies retrieving odds from these platforms but does not explicitly state an action like 'get' or 'retrieve'. It provides some domain context but is too vague to clearly define the tool's purpose.

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?

No guidance on when to use this tool versus siblings such as get_price, get_sentiment, or other 'get_' tools. There is no mention of use cases, prerequisites, or alternatives.

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