get_market_trades_events

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

No annotations are provided, so the description carries the full disclosure burden. It conveys that this returns a live stream of trades plus lifecycle events, which is useful behavioral context, but says nothing about auth requirements, rate limits, or mutability. Output formatting is covered by the output schema, so that gap is acceptable.

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?

Purpose is front-loaded in the first sentence, with the argument detail following in an Args block. No filler, though the Args formatting is slightly heavier than a one-parameter tool strictly needs.

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?

The tool is simple (one required parameter) and an output schema covers return values, so the description need not explain them. It documents the lone parameter and the live-stream nature adequately; the main omission is explicit usage routing against siblings.

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?

With 0% schema description coverage, the sole parameter is documented only by its bare title in the schema. The description compensates by explaining that condition_id is the unique on-chain identifier for the market's conditions, adding meaning beyond the schema.

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?

States a specific verb ('Fetch') and resource ('stream of live trade activity and lifecycle events') scoped to a specific prediction market. The word 'live' implicitly distinguishes it from historical siblings, but it never names an alternative sibling to sharpen the distinction.

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?

There is no explicit when-to-use guidance and no comparison against alternatives like get_trade_history or get_activity. The only routing signal is the implied 'live' vs historical framing, which an agent must infer.

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