watch_book

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

Annotations already cover the read-only, idempotent, non-destructive nature, and the description adds behavioral detail: streaming is bounded by seconds (1-60) or max_events, and the tool returns the collected events afterward. It also warns about quiet-market behavior, which is useful beyond the 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?

Two sentences deliver resource, event types, termination conditions, usage sequencing, and an expectation-setting caveat with no filler. The most important operational facts are front-loaded.

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 read-only streaming tool with a small schema and no output schema, the description covers what events are returned, what terminates the stream, and how it fits into the get_orderbook workflow. It could specify the exact return shape, but the event types and bounded-stream semantics are sufficient for invocation.

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?

Despite 0% schema description coverage, the description clarifies token_id as the target Polymarket token and explains how seconds (1-60) and max_events act as termination limits. It does not restate defaults, but the schema already provides those values.

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?

Description states a specific verb ('stream') and resource ('one Polymarket token's realtime market events') and enumerates event types (book snapshot, price changes, trades). It clearly distinguishes itself from get_orderbook by emphasizing book movement.

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?

Explicitly says to use it after get_orderbook when the agent needs to see the book move before acting, and sets expectations that a quiet market may only return the initial snapshot. This provides both a sequencing cue and a condition for when the tool is appropriate.

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