getPredictionEventDetail

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

No annotations provided, but the description thoroughly discloses the tool's behavior: it returns detailed info, includes outcome token IDs, current prices, and statistics. It also explains the slug priority and hasMoreMarkets parameter effect. No contradictions.

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 redundancy (e.g., 'Agent hint' repeats earlier info) and could be more streamlined. It is adequately structured but slightly verbose.

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 or output schema, the description provides a fairly complete picture: what the tool does, when to use it, parameter usage hints, and sibling avoidance. It could mention response format or rate limits, but overall sufficient.

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 description coverage is 0%. The description adds meaning by explaining slug is for human-readable lookups (takes priority), eventId as alternative, and hasMoreMarkets to include sub-events. However, it doesn't provide exhaustive details beyond the schema types.

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 it retrieves detailed information about a prediction event, including markets, outcome tokens, prices, and trading statistics. It distinguishes from sibling tools by specifically advising not to use getPredictionMarketList for individual event details.

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?

Explicitly states when to use (before placing orders to get token IDs and prices), explains priority of slug over eventId, and provides agent hints. It also includes a clear directive to avoid getPredictionMarketList for this purpose.

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