subscribe_latest_news

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: WebSocket connection, real-time updates, duration-based collection (wait_seconds), and filtering capabilities. However, it lacks details on error handling, connection stability, or authentication needs, which are important for a WebSocket tool.

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 well-structured with a purpose statement followed by a bullet-point list of parameters. It is front-loaded with the main action and avoids unnecessary details. However, the parameter list could be more integrated into the narrative for slightly better flow.

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 no annotations and no output schema, the description covers the tool's purpose and parameters well but lacks details on return values, error cases, or WebSocket-specific behaviors like connection handling. For a real-time subscription tool with 5 parameters, this leaves some gaps in 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?

Schema description coverage is 0%, so the description must compensate. It provides clear semantics for all 5 parameters: wait_seconds (duration to listen), max_items (limit on collected items), coins (filter by symbols), engine_types (filter format), and has_coin (boolean filter). This adds significant meaning beyond the basic schema.

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 clearly states the tool's purpose: 'Subscribe to real-time news updates via WebSocket' with specific actions like 'connects to the WebSocket feed, subscribes to news with optional filters, and collects incoming messages'. It distinguishes from sibling tools (e.g., get_latest_news, search_news) by emphasizing real-time subscription via WebSocket rather than one-time retrieval.

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 implies usage for real-time news updates with filtering, but does not explicitly state when to use this tool versus alternatives like get_latest_news or search_news. It provides context for real-time collection but lacks explicit exclusions or named alternatives.

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