api_monitor_wait_for_traffic

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

With no annotations, the description carries full behavioral burden. 'Wait for ... then return' implies a blocking call, which is genuinely useful, but it omits timeout semantics (the timeout_seconds param), what happens on timeout, and whether the wait is polling-based or event-driven. These are exactly the traits an agent needs for a long-running blocking 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?

A single front-loaded sentence with no filler, which is structurally clean. But 'concise' here shades into under-specification: one sentence is too thin for a 5-parameter blocking tool with zero schema documentation, so it is not appropriately sized for its complexity.

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?

An output schema exists, so return values need not be described. Everything else is missing: no parameter guidance at 0% schema coverage, no annotation coverage, and no explanation of the blocking/timeout contract that defines this tool's behavior relative to its ~50 siblings.

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% across 5 parameters, so the description must compensate and largely does not. 'call count' faintly hints at minimum_calls and 'traffic panes' faintly at limit, but limit, window_title, window_handle, and timeout_seconds receive no explanation of defaults, units, or targeting behavior.

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?

States a verb+resource ('wait for ... then return the current traffic panes'), which distinguishes it from a plain read of api_monitor_traffic by implying blocking behavior. However, 'Rohitab Summary call count' is opaque jargon and 'traffic panes' is not defined, so the agent cannot be fully certain what is returned or which subsystem it targets.

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 indication of when to prefer this over api_monitor_traffic, api_monitor_summary, or api_monitor_traffic_details, all of which appear in the sibling list. No prerequisites, no statement of what condition makes the wait succeed or fail.

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