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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses sort order, server-side filtering/pagination, eviction limits, behavior when channels are removed, q's time-budget and continuation semantics, and the meaning of stored/rejected/discarded outcomes.

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 dense but each sentence carries useful information: order, pagination, result meanings, retention, q behavior, and a pointer to the single-batch endpoint. It is front-loaded with the core purpose, though slightly long.

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?

For a list tool with 8 parameters and no output schema, the description explains the essential behavior, result states, retention, and search semantics, making the response shape predictable. It stops short of specifying a return envelope or auth requirements, but these are partially covered by the schema and the list context.

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%, so the baseline is 3. The description adds real meaning beyond the schema by explaining q's search scope (metric names, NCPA host/service), the time-budget behavior, and search.complete continuation. Other parameters remain adequately self-documented by the 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 states exactly what the tool does: lists batches a collector sent, newest first, with server-side filtering and pagination. It distinctly separates this from opening a single batch by pointing to the dedicated GET endpoint for a batch, so an agent can tell this list operation apart from get_device_input_batch.

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 gives rich context about filtering by date, outcome, and q, as well as pagination and retention behavior. It implicitly points to an alternative for opening one batch, but it never explicitly says when to prefer this tool over siblings or when not to use it.

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