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

Annotations already cover the read-only/idempotent/non-destructive safety profile, and the description adds substantial context beyond them: an auth gate requirement, a no-wager guarantee, hard capture bounds (5 seconds, 50 messages, 256 KiB), and an explicit caveat of no guaranteed opportunities or continuous coverage. This is exactly the kind of behavioral disclosure the annotations don't carry.

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?

It is front-loaded with the core action and stays dense – each sentence contributes a distinct fact (access, no-wager, limits, caveats). Slightly thick for the payload but nothing is redundant filler.

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?

An output schema exists, so return values need not be explained, and the behavioral limits are well covered. The real gap is a fully undocumented nested parameter set that the description does nothing to clarify, leaving an agent under-informed on how to actually construct the capture request.

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 0% and the schema contains a nested filters object with six sub-fields (sources, event_ids, min_percent, include_live, affiliate_ids, include_links) plus max_frames and duration_ms. The description only loosely gestures at 'selected events and books' and never explains any parameter's meaning, so it fails to compensate for the coverage gap.

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 and resource: 'Read actual frames from the dedicated V2 hedge WebSocket for selected events and books.' The word 'V2 hedge' distinguishes it from the nearby capture_v1_stream/capture_live_stream/capture_market_stream siblings, but the description never names those alternatives explicitly, so the differentiation is implicit rather than stated.

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?

It notes the access precondition ('Requires HedgeAccess or an eligible pass; this dedicated route has its own gate') and clarifies that it places no wagers, which frames usage somewhat. However, it gives no explicit when-to-use-vs-alternatives guidance against the three sibling capture_* tools, so the agent must infer which stream to pick.

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