watch_prices

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

With no annotations, the description alone must disclose behavioral traits. It only says 'Watch live midpoint prices' but does not explain whether this is a one-time fetch or a live subscription, whether it has side effects, if authentication is required, or any rate limits. The agent gets no meaningful behavioral context beyond the literal action.

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 description is extremely concise with no filler. The core purpose is front-loaded, and parameter explanations are minimal but necessary. Each sentence serves a purpose.

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 with only two parameters, and an output schema exists (though not shown). The description explains the parameters but lacks context on when to invoke it, expected behavior, or return format nuances. For a simple observation tool, it is minimally adequate but leaves gaps in usage guidance.

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 coverage is 0%, so the description must compensate. It explains that 'slugs' are comma-separated market slugs or condition IDs, and 'outcomes' are comma-separated outcomes with a default. This adds meaning beyond the parameter names, though it does not detail acceptable values or edge cases.

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 clear action ('Watch live midpoint prices') and resource ('one or more markets'), which is specific and understandable. It does not explicitly differentiate from sibling tools, but the tool name and description make its purpose self-evident among buy/sell/portfolio tools.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or contexts. There is no indication of when to prefer watch_prices over other price-related tools like get_market or get_order_book.

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