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

The description states that setting 'mark_read:true' flags returned events as read, implying a state mutation. This contradicts the annotation 'readOnlyHint:true', which asserts no state changes. Per scoring rules, a contradiction warrants a score of 1.

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 three sentences, front-loaded with the core purpose. It efficiently conveys key details and an alternative endpoint without extraneous words. Minor improvement could be to group return fields more concisely.

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?

Given no output schema, the description adequately explains return fields (source, citation_uri, raw event payload) and covers the tool's behavior (filtering, polling, alternative access). It lacks details on ordering or pagination but is sufficient for a simple list tool.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by explaining the effect of 'mark_read' (flags events read so next call shows only newer ones) and mentions filtering by 'type' and 'since', going slightly beyond the schema's dry parameter 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 uses the specific verb 'Pull' and identifies the resource 'fired events from your subscription feed', clearly stating what the tool does. It distinguishes itself from sibling tools like 'list_subscriptions' or 'subscribe' by focusing on events from the feed.

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 mentions that polling works fine and provides an alternative REST endpoint ('GET registry.pipeworx.io/alerts.json') for scripts and dashboards, giving context on when to use this tool versus the API. However, it does not explicitly state when not to use it or compare to other sibling tools for similar tasks.

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