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

No annotations are supplied, so the description carries the full behavioral burden and does so: it discloses that the oww_ token is one-time, that tokens are invalid after close, and that begin costs 500 credits / $0.500 while in-window poll and close are free and snapshot/history are 20 credits. It also notes which deprecated tool names are absorbed, which matters for an agent choosing among near-identical siblings.

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 purpose and the branching model are front-loaded in the first two sentences, and the prohibitions and metering follow in a logical order. It is dense but nearly every clause carries distinct information; the metering sentence is long but genuinely decision-relevant for a paid call.

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?

For a 7-parameter, 5-branch tool with no output schema, the description covers return values per branch (signal/series, windowId plus token and expiry, poll signal or close summary), costs, and token lifecycle. The remaining gap is the un-explained optional parameters (days, interval, window_id) that determine history and window behavior.

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 only 43%, and the description compensates for the hardest part by explaining what each op value means and where windowId and the oww_ token come from. However, it adds no meaning for days, interval, or window_id beyond the schema, leaving several low-coverage parameters undocumented in either place.

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 names a specific resource (Oracle Watch trust signals) and enumerates the five branches it multiplexes: snapshot, history, begin, poll, close. It also explicitly distinguishes itself from the sibling trade_guard (op check_safety), so an agent can tell the two apart without opening either schema.

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 gives explicit when-to-use (read one snapshot or history series, buy a 24h window, poll/close a purchased window) and explicit when-not-to-use (pre-trade safety belongs to trade_guard). It also states two hard constraints: do not buy a second window for the same subject and never reuse a token after close.

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