Does 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.

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

No annotations are provided, so the description carries the full behavioral burden and largely drops it. It does not say whether subscribing is idempotent, whether it requires GitHub auth or specific scopes, whether events accumulate into 'pending_events', how long the watch persists, or what the response contains.

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?

One short, front-loaded sentence with zero wasted words. It is arguably too terse given how much behavioral information is missing, but there is no padding or burying of the key point.

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 sibling tools that clearly interact with this one ('unsubscribe', 'subscriptions', 'pending_events'), an agent needs to know how subscription state and events flow. None of that lifecycle context is present, leaving the definition under-specified for its role.

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 single parameter 'pr' is fully documented in the schema (URL or OWNER/REPO#NUMBER), so the high coverage baseline of 3 applies. The description adds no format examples, validation notes, or edge-case guidance beyond what the schema already states.

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 ('watch') and resource ('GitHub pull request') and adds the purpose ('for new activity'), so the intent is unambiguous. It does not explicitly differentiate itself from the sibling 'unsubscribe' or explain the relationship to 'pending_events', so it falls short of a 5.

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 phrase 'for new activity' implies the use case of monitoring a PR, but there is no explicit when-to-use, no prerequisites (auth scope, whether a subscription must be unsubscribed first), and no mention of the alternatives that the siblings 'unsubscribe' and 'subscriptions' provide.

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

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

No annotations are provided, so the description carries the full behavioral burden. It does add the useful scoping detail that results are limited to what *this session* has watched, but it omits ordering, size limits, and what the entries contain.

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 sentence with zero waste, front-loaded with the verb and resource, and carrying the one qualifier that matters (session scope).

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 tool is trivially simple — no parameters, no annotations, no output schema — so the description is not dangerous, but with no output schema it should at least sketch what a listed pull request looks like or in what order they return. As written the agent knows what it gets in aggregate but not the shape of the result.

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 there is nothing for the description to disambiguate; baseline 4 applies. The only semantic content is the scope of the list, which the description does state.

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 pair ('List pull requests watched by this session') and the session scoping implicitly separates it from the subscribe/unsubscribe siblings, which mutate that watch list. It does not explicitly name those siblings, so an agent still has to infer the pairing.

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?

Usage is only implied: the description makes clear this is the read side of the subscribe/unsubscribe pair, but it never says when to call it versus pending_events, nor whether it is safe to call at any time. No explicit when/when-not guidance.

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

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

With no annotations at all, the description carries the full burden for a state-mutating tool, yet says nothing about idempotency, auth requirements, whether it errors on a non-subscription, or what the response looks like. Only the bare intent is conveyed.

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?

One short, front-loaded sentence with zero waste. It is somewhat under-specified rather than padded, but structure-wise nothing is wasted.

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 an annotation-free mutation tool with no output schema, the description should cover success/failure semantics and subscription state implications. None of that is present, leaving meaningful gaps an agent would hit at call time.

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 single parameter `pr` is fully documented in the schema (GitHub PR URL or OWNER/REPO#NUMBER), so the 100% coverage baseline of 3 applies. The description adds no format or scoping detail beyond 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?

"Stop watching a pull request" is a specific verb plus resource, and reads clearly as the inverse of the sibling `subscribe`. It doesn't explicitly name or contrast with that sibling, so the differentiation is inferable rather than stated.

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 `subscribe` or `subscriptions`, no prerequisites, and no mention of what happens when the user isn't subscribed. The agent must guess at the operational context.

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