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

The description directly contradicts the annotations. Annotations declare readOnlyHint=true, but the description says 'Set mark_read:true to flag returned events read so the next call only shows newer ones', which is a state-changing write. This is a serious inconsistency that undermines agent trust.

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 well-structured: the first sentence states the core purpose, followed by details on return payload, filtering, mark_read, and alternative access. It is slightly dense but each sentence contributes useful information without excessive verbosity. It does not repeat schema descriptions unnecessarily.

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?

The description covers return format (source, citation_uri, raw payload), filtering, mark_read behavior, and alternative endpoint access. However, it omits interaction between parameters (e.g., unread_only vs mark_read) and does not mention the default limit or range, though these are in the schema. The annotation contradiction further reduces completeness, as the behavioral contract is inconsistent.

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 meaningful semantics beyond the schema: it gives a concrete example filter value ("sec_8k"), clarifies the use of 'since' as ISO timestamp, and explains the effect of mark_read:true (next call only shows newer events). This enriches the schema's descriptions.

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 purpose: 'Pull fired events from your subscription feed' and 'Returns the most recent alerts'. It specifies the resource (subscription feed alerts) and the action (pull/return), distinguishing it from siblings like recent_changes. It also mentions key aspects like filtering and mark_read behavior.

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 usage context: it says 'Filter by type (e.g. "sec_8k") and/or since (ISO timestamp)' and 'Polls work fine', indicating suitable scenarios (polling, filtering). It also points to an alternative access method (GET registry.pipeworx.io/alerts.json) for scripts/dashboards. However, it does not explicitly contrast with sibling tools or state when not to use it.

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