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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful context beyond annotations by specifying 'live' (real-time) and 'taker volume' measured in 'shares', but it does not disclose potential caching, rate limits, or aggregation behavior. No contradiction with annotations.

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?

A single sentence that front-loads the action and resource, with no redundant phrasing. It is concise while conveying scope and units, and every word adds value.

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 single self-descriptive parameter, a provided output schema, and strong annotations, the description is nearly complete for a basic read operation. The only notable omission is guidance on how to source eventId, which is a minor gap for invocational completeness.

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 description must compensate for the single eventId parameter. It only implies that eventId identifies 'one event' but does not explain how to obtain the eventId, its format, or any relationship to other tools like list_events. This is a clear 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?

The description states a specific verb ('Get'), resource ('live taker volume for one event and its markets'), and measurement unit ('shares'). It clearly distinguishes this from sibling tools like get_market_trades or get_open_interest by specifying it is event-scoped and volume-focused.

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 phrase 'for one event and its markets' gives clear context that this tool is for a single event and its submarkets, not a wallet or market-level query. However, it does not explicitly name alternatives or state when not to use it, leaving some inference to the agent.

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