Retrieve queued GitHub pull request activity and report any events lost when the queue limit was reached.
Read pending events and report any events dropped at the queue limit.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 carries the full burden. It mentions reporting dropped events but never says whether reading consumes/removes pending events, what auth is needed, or what the response looks like — a major gap for a queue-reading tool that may be stateful.
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; the primary action is stated first and the secondary reporting behavior follows. Brevity is appropriate for a zero-parameter tool, though the sentence is a bit thin given the behavioral unknowns.
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?
With no annotations, no output schema, and no sibling routing guidance, the description does not cover enough: the critical question of whether reading pending events drains the queue is unaddressed, and the return shape of the dropped-events report is unspecified.
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?
The tool takes zero parameters, so the baseline is 4. The description correctly implies no inputs are needed, and there is nothing further to clarify.
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 specific verb and resource (read pending events) plus a secondary behavior (report dropped events at queue limit), so the agent knows exactly what operation this is. It does not explicitly distinguish itself from siblings like subscribe/unsubscribe, though the read semantics imply the difference.
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 on when to use this versus the subscription-management siblings, nor any preconditions or exclusions. Usage is only implied by the name and the phrase 'read pending events'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.