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

There is a direct contradiction with the annotations: readOnlyHint=true conflicts with the description's disclosure that setting mark_read:true will flag events as read, modifying state. The description otherwise provides useful context (payload fields, polling safety), but the contradiction invalidates transparency.

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 compact and front-loaded with the primary action. Each sentence adds necessary information: return content, filtering, mark_read behavior, and the alternative feed URL. 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?

Despite no output schema, the description explains what each returned event carries (source, citation_uri, raw payload) and covers the key parameters. However, it does not mention limit or unread_only, though those are in the schema. The contradiction with annotations also slightly undermines overall completeness, but the description itself is sufficiently informative for a polling 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?

The schema already has 100% coverage with descriptions for all parameters, but the tool description adds valuable clarification: it gives a concrete type filter example ("sec_8k") and explains the mark_read side effect in operational terms, exceeding the schema's baseline.

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 tool's function: pulling fired events from a subscription feed. It specifies the resource (alerts feed) and the action (pull), and distinguishes itself from sibling tools by focusing on alert retrieval rather than subscription management or other data.

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 notes that polling works fine and offers an alternative endpoint (registry.pipeworx.io/alerts.json) for scripts and dashboards, implying the tool is for agent-context use. It also explains mark_read behavior for subsequent calls, but does not explicitly contrast with sibling tools like list_subscriptions or recent_changes.

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