get_prediction_event_detail

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

No annotations provided, so description carries full burden. Discloses that large events can have 100+ sub-markets and return large responses. Does not mention authentication or rate limits, but the behavioral trait of response size is clearly communicated.

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?

Two sentences: first states purpose, second warns about large events and parameter usage. No filler, every sentence adds essential information.

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?

No output schema, but description lists return elements (sub-markets, probabilities, rules, settlement timing). Adequately covers input parameters with warning. Could mention error handling, but sufficient for tool selection.

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 has 100% description coverage. Description adds value beyond schema by explaining the warning about large events and advising on markets_limit usage ('Increase only when you need full coverage').

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?

Clearly states 'Get full details for one prediction market event' with specifics (sub-markets, outcome probabilities, rules summary, settlement timing). Distinguishes from sibling tools like search_prediction_events and get_prediction_market_quote.

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?

Provides explicit warning about large events and guidance on markets_limit default and adjustment. Lacks explicit when-not-to-use or alternatives, but warning implies cautious usage.

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