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

The description clearly discloses that setting mark_read:true mutates the read state of events, which is a behavioral trait. However, the annotations declare readOnlyHint=true, which implies no state mutation occurs. This contradiction reduces transparency, as the agent cannot rely on the annotations alone. The description adds some context beyond annotations (e.g., return structure) but is undermined by the inconsistency.

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 (4 sentences) and front-loaded with the core purpose. Every sentence adds essential information without redundancy. The structure flows logically: purpose → return format → filtering → side effects → alternative access.

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 the 5 optional parameters and no output schema, the description adequately explains the return format (source, citation_uri, raw payload) and filtering behavior. It also mentions an alternative access method. However, it does not specify pagination behavior for large result sets beyond the limit parameter, which could be considered a minor gap 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 input schema already covers all 5 parameters with descriptions (100% coverage). The description adds value by explaining usage context, such as 'set mark_read:true to flag returned events read so the next call only shows newer ones', which goes beyond the schema's static description. It also reiterates key constraints like default limit.

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 opens with a specific verb-resource pair ('Pull fired events from your subscription feed') and details what is returned (source, citation_uri, raw payload). It clearly distinguishes itself from sibling tools like list_subscriptions or subscribe by focusing on reading alert 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 explains when to use the tool (to fetch recent alerts) and provides context for polling suitability. It also mentions an alternative access method (GET registry.pipeworx.io/alerts.json) for scripts/dashboards. However, it does not explicitly state when not to use it relative to other tools.

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