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, which is a state-changing operation. However, annotations include readOnlyHint: true, indicating no modifications. This is a direct contradiction, severely undermining transparency. The description also discloses that each event carries source and URI, but the contradiction is disqualifying.

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 four sentences, front-loaded with the main purpose. Every sentence adds value: purpose, return format, filtering options, mark_read behavior, and alternative access. No wasted words.

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 5 optional parameters and no output schema, the description explains the return format (source, citation_uri, payload) and provides context for polling and alternative access. However, the contradiction with annotations makes the description less trustworthy, and it does not clarify idempotency or error cases.

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%, and each parameter has a description. The description adds examples (e.g., 'sec_8k') and clarifies that since is an ISO timestamp, but these add marginal value over the schema descriptions. The description does not compensate for any missing schema detail.

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 clearly states the action ('Pull') and the resource ('fired events from your subscription feed'), and it specifies what each alert carries (source, citation_uri, payload). It distinguishes itself from siblings by focusing on recent alerts from a persisted feed, which is unique among the listed tools.

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 access method (GET registry.pipeworx.io/alerts.json), but it does not explicitly state when to use this tool vs. sibling tools like list_subscriptions or search_within. Usage context is implied but not fully guided.

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