Get full prediction-market event detail

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint. The description adds valuable context: it is free, returns cross-venue matches and reference probability, and includes volumeHistory. It does not contradict annotations and provides behavioral details beyond them.

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 slightly lengthy but well-structured, front-loading key information (free public detail) and then enumerating the returned fields. Every sentence adds value, though some minor trimming could improve conciseness.

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 tool has an output schema, the description adequately explains what the response contains (outcomes, crossSourceMatches, referenceProbability, whale trades, etc.). It covers the complexity of cross-venue research and volume trends, making it complete for the tool's purpose.

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 100% with all three parameters described (fiat, slug, source). The description does not add parameter-specific details beyond the schema, but the baseline score of 3 is appropriate since the schema already provides sufficient documentation.

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 prediction-market event detail by venue and slug, listing specific data fields like outcomes, probabilities, crossSourceMatches, etc. It distinguishes from the sibling pm_quote by explicitly calling this the 'cross-venue research view' and noting pm_quote is for 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?

Provides explicit when-to-use guidance: 'This is the cross-venue research view; for tradability use pm_quote.' Also states 'No API key required,' indicating no authentication needed. This helps the agent select the correct tool based on the task's purpose.

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