Get full prediction-market event detail

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds context beyond annotations by detailing the rich data returned (crossSourceMatches, referenceProbability, volumeHistory) and how to interpret them, but doesn't contradict any annotation.

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 a single paragraph that is informative but dense. It front-loads the core purpose and adds layered details. Could be slightly more structured, but overall efficient for a complex tool.

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 the complexity of the returned data and the presence of an output schema (though not shown), the description thoroughly explains key fields (crossSourceMatches, referenceProbability, volumeHistory) with usage guidance. It addresses the tool's role fully.

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 100%, so the input schema adequately documents the three parameters. The description mentions 'venue + slug' but adds no new semantics beyond what the schema provides. Baseline 3 is appropriate.

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 retrieves full details for a single prediction-market event by venue and slug. It enumerates specific data points (outcomes, probabilities, price snapshots, etc.) and distinguishes itself from the sibling tool pm_quote by noting this is the 'cross-venue research view' vs. 'tradability'.

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 says when to use ('cross-venue research') and when not to ('for tradability use pm_quote'). Also notes no API key required and that it's free public detail, providing clear context for invocation.

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