stream_market

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

Discloses key behavioral traits: WebSocket connection, returns first change event, times out, requires slug. No annotations provided, so description carries full burden. Missing details on error handling or connection lifecycle, but adequate for basic usage.

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 with no waste. First sentence front-loads core functionality and method. Second sentence adds timeout and identifier requirement. Highly efficient.

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?

Covers all essential aspects for a simple watch tool: action, method, timeout, identifier distinction. Lacks output structure description, which could be inferred. No annotations to supplement. Adequate for the tool's simplicity.

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 100%, but description adds value by clarifying that slug is the market slug, not the market app ID. Timeout default is noted. Adds meaningful context beyond schema descriptions.

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?

Clearly states verb (watch), resource (single market), method (WebSocket), and output (first change event). Explicitly distinguishes the identifier (slug vs app ID) from potential confusion.

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?

Describes the core usage (watch single market via WebSocket) and timeout behavior. Does not explicitly state when not to use or name alternatives, but sibling tool names provide implicit guidance.

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