Page through captured USB PD events starting at a specified index and return the next index for continued reading.
Page through captured PD events from index since; next is the next index to ask.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| since | No | ||
| decode | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral burden. It discloses pagination semantics but omits whether the tool is read-only, whether reading consumes or clears the capture buffer, and what happens when no more events remain.
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 a single front-loaded sentence with no filler. Every element contributes to explaining the pagination model.
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?
There is no output schema and no annotations, and the description does not explain the return shape beyond `next`, the meaning of `decode`, buffer behavior, or prerequisites. It is too sparse for a three-parameter tool with no structured documentation.
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%, and the description explains only `since` and the output `next`. It leaves `limit` and `decode` completely undocumented, so it fails to compensate for the missing 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?
The description states a specific verb, "Page through," and resource, "captured PD events," and explains the pagination index. It distinguishes reading from the capture-start/stop siblings, though "PD" remains somewhat domain-dependent.
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?
It implies repeated paging by mentioning `since` and `next`, but gives no explicit when-to-use guidance, no prerequisites such as starting a capture first, and no comparison to siblings like pd_capture_start or pd_status.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.