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

The description states mark_read:true flags events as read and affects future calls, which mutates feed state. Annotations declare readOnlyHint:true and idempotentHint:true, directly contradicting this behavior. This is a clear annotation contradiction, so transparency scores 1.

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?

Four sentences, each earning its place: purpose, return payload shape, filtering/mark_read behavior, and polling/alternative endpoint. No filler, front-loaded with the core action.

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 schema covering parameter details and annotations covering safety intent, the description completes the picture with return payload fields, stateful mark_read behavior, and an external endpoint. It does not repeat limit or unread_only semantics, but those are already in the schema. Slight deduction for not mentioning the public availability of the alternate endpoint, though it is implied.

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 covers all 5 parameters with descriptions (100% coverage). The description adds value by providing a concrete type example ('sec_8k'), explaining the mark_read effect on subsequent calls, and clarifying the since parameter with ISO timestamp, which goes beyond bare schema definitions.

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: 'Pull fired events from your subscription feed.' It clearly states the scope (most recent alerts written to a persisted feed) and distinguishes from siblings like list_subscriptions and recent_changes by focusing on fired events with a persistent feed. The alternative endpoint mention further clarifies its role.

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?

It gives clear context for when to use the tool (polling the subscription feed) and even points to a script/dashboard alternative (registry.pipeworx.io/alerts.json). However, it does not explicitly name sibling tools to exclude, so while context is strong, exclusions are implied rather than stated.

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