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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether this is read-only or mutating, whether authentication or permissions are required, whether there are side effects, or what the response shape is; the 'coin flip' phrasing does not clarify behavior.

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 two sentences and front-loads 'Market trials,' with the sibling pointer placed at the end. The parenthetical market list is long but bounded, and there is no obvious filler, though the second clause is cryptic rather than clarifying.

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?

With no annotations, no output schema, and no parameters, the description must fully orient the agent. It gives a market scope and one sibling exclusion, but omits what calling the tool actually does and what it returns, leaving the agent unable to invoke it with confidence.

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?

The tool has zero parameters, so there is no parameter meaning for the description to add. The empty schema is fully described by the structural definition, and the description neither helps nor harms parameter understanding.

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 labels the resource as 'Market trials' and describes a broad market scope, but never states a concrete action such as list, read, or measure. Phrases like 'every belief measured... against a coin flip' and 'what each market's rules can ask about' are jargon-heavy and leave the core purpose ambiguous, though the final sentence does distinguish it from opsin_markets for Elysium launches.

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?

The only usage signal is the exclusion 'Launches on Elysium are in opsin_markets.' There is no guidance on when to use this tool, what preconditions exist, or how it relates to alternatives like opsin_perp_preview, opsin_market_preview, or opsin_markets beyond that single split.

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