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

Even though annotations already declare readOnlyHint and idempotentHint, the description goes further by disclosing the optional mark_read side effect ('flag returned events read so the next call only shows newer ones') and describing return fields like source and citation_uri. This adds context beyond the structured annotations and avoids any contradiction.

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 three sentences, front-loaded with the core action, and every sentence adds useful information (purpose/return fields, filters, mark_read behavior/alternative endpoint). No filler or redundancy.

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?

For a 5-parameter read tool with no output schema, the description covers the essential return format (payload fields), filter options, the read-state mutation, and even an alternative access method. Combined with full schema descriptions and safe annotations, this is highly complete.

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 a baseline of 3 applies. The description adds value by providing an example type filter ('sec_8k'), clarifying the ISO timestamp format for 'since', and explaining the practical effect of mark_read (affects subsequent calls). This is above baseline, though not exhaustive for all parameters.

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 'Pull fired events from your subscription feed.' This is a specific verb+resource statement that clearly distinguishes it from siblings like list_subscriptions (managing subscriptions) or recent_changes (change logs). It also specifies the return payload contents, making the tool's scope unambiguous.

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 gives clear usage context: it's for retrieving recent alerts from a persisted feed, with filtering by type and since. It also suggests polling is fine and mentions an alternative HTTP endpoint for scripts/dashboards. However, it doesn't explicitly call out when to avoid this tool or name direct alternatives from the sibling tool set, so it loses one point.

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