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

Annotations already declare readOnlyHint=true, idempotentHint=true, etc. The description adds useful behavioral details like the payload structure and the effect of mark_read:true. However, mark_read:true implies state mutation (marking events as read), which contradicts the readOnlyHint annotation. This reduces transparency and trustworthiness.

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 three sentences, each serving a distinct purpose: stating the core function, describing return payload and filtering, and explaining the mark_read usage and an alternative access method. No redundant information exists.

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 tool has 5 parameters (all optional), no output schema, and annotations covering safety, the description provides a good overview of purpose, return structure, filtering, and a usage example. It could mention limit and unread_only parameters briefly, but the schema covers them. Overall, fairly 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 the schema already describes parameters. The description adds value by giving an example for type ('sec_8k'), specifying ISO timestamp format for since, and explaining the effect of mark_read. This goes beyond the schema alone, justifying a score above the baseline of 3.

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 pulls fired events from a subscription feed and specifies what each event carries (source, citation_uri, payload). However, it does not explicitly distinguish this tool from siblings like list_subscriptions or subscribe, which could cause confusion about which tool to use for similar tasks.

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 clear usage context: filtering by type and since ISO timestamp, marking events as read to advance the feed, and that polling is fine. It also mentions an alternative access method (direct REST endpoint for scripts/dashboards), but lacks explicit when-not-to-use guidance or comparison with sibling tools.

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