Listen Debug

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

With no annotations provided, the description carries full behavioral burden. It mentions WebSocket but fails to disclose whether the tool blocks or is asynchronous, how results are returned (e.g., stream vs. batch), or resource implications. Important behaviors like cancellation or timeout handling are omitted.

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 short and not verbose, but it sacrifices necessary details for brevity. While concise, it does not fully earn its place as it leaves key questions unanswered.

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 description is incomplete given the tool's complexity (streaming data via WebSocket). It does not explain the return format, how to stop listening, or behavior on duration expiry. With no output schema, more descriptive detail is needed.

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 67% (2 of 3 parameters described). The description adds no new meaning beyond the schema; for example, 'duration' lacks unit or behavior explanation. Given coverage below 80%, the description should compensate but does not.

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 action (capture), the resource (debug messages), the mechanism (via WebSocket), and a constraint (specified duration). It is specific and effectively distinguishes from other tools, as no sibling tool directly handles debug message capture.

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?

No guidance is given on when to use this tool versus alternatives, or any prerequisites. It implicitly suggests use for listening to debug messages, but lacks context such as requiring a running Node-RED instance or WebSocket support.

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