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

Annotation Contradiction: The annotations declare readOnlyHint=true, but the description explicitly states that setting mark_read:true flags returned events as read, which mutates state and affects subsequent calls. This directly contradicts the read-only annotation, making the behavioral disclosure inconsistent and unreliable.

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 moderately sized and front-loaded with the core purpose. It covers return format, filtering, mark_read behavior, and external access in four sentences. A compact but complete summary, though it could be slightly tightened without losing essential information.

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 output schema, the description adequately describes return values (each event carries source, citation_uri, raw payload). It covers query parameters, side effects, and alternative access. It does not mention pagination or limit/unread_only defaults, but these are adequately documented in the schema, so completeness is high.

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%, so baseline is 3. The description adds value by explaining the 'type' example ('sec_8k'), the 'since' format (ISO timestamp), and the behavioral effect of 'mark_read' (next call shows only newer events). These enrich the parameter understanding 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?

The description uses a specific verb ('Pull') and resource ('fired events from your subscription feed'), and clearly distinguishes itself from siblings like list_subscriptions by focusing on alert events rather than subscriptions. It also specifies the return content (source, citation_uri, payload), leaving no ambiguity about what the tool does.

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 provides clear usage context: it says polling works fine and mentions an alternative access method (GET registry.pipeworx.io/alerts.json) for scripts and dashboards. It does not explicitly name sibling tools to exclude, but the guidance on when to use and the external fallback gives practical direction.

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