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

Annotations already declare readOnlyHint and idempotentHint, but the description adds important context: setting mark_read to true modifies state (flags events as read), affecting subsequent calls. This explains a non-obvious side effect beyond the annotations, enhancing 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 concise with about five sentences, front-loading the main action. It efficiently covers purpose, return contents, filtering, and state modification. No superfluous text, though could be slightly more structured.

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 payload). All parameters are covered, and the tool's role among many siblings is clear. A minor gap: it doesn't mention pagination or the default limit, but overall sufficient.

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?

All five parameters have schema descriptions (100% coverage), so the description's contribution is marginal. It does elaborate on mark_read's effect ('so the next call only shows newer ones'), but overall adds little 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 starts with a specific verb ('Pull') and resource ('fired events from your subscription feed'), clearly stating the tool's purpose. It also distinguishes itself by mentioning an alternative access method (GET registry.pipeworx.io/alerts.json) and implies no user/workspace filtering, helping differentiate from potential sibling 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 explains when to use the tool (pulling recent alerts, polling) and mentions an alternative for scripts and dashboards. It does not explicitly state when not to use it, but the context is clear enough. The mention of filtering options and mark_read behavior provides practical guidance.

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