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

The annotations already indicate readOnlyHint=true (read-only), idempotentHint=true, and destructiveHint=false. The description adds value by explaining the side effect of mark_read (flagging events as read so next call shows newer ones) and the availability of an external endpoint, which are not covered by annotations alone. No contradictions are present.

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 four sentences long, each serving a distinct purpose: purpose, return fields, filtering/mark_read usage, and alternative access. It is front-loaded with the core action and avoids redundancy with structured fields. Every sentence adds value with no wasted words.

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 read-only list tool with 5 optional parameters and no output schema, the description covers all necessary aspects: what is returned, how to filter, the mark_read side effect, and even an alternative REST endpoint for non-LLM use. It is self-contained and sufficient for an agent to use correctly.

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 documentation covers 100% of parameters, so baseline is 3. The description enhances understanding by providing examples ('type e.g. sec_8k') and clarifying that since is an ISO timestamp. This adds practical context beyond the schema's property 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 uses a specific verb ('Pull') and resource ('fired events from your subscription feed'), clearly distinguishing it from sibling tools like 'search' or 'recent_changes'. It also lists the key return fields (source, citation_uri, payload), which adds specificity.

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 mentions that polling works fine and points to an alternative REST endpoint, providing some context on when to use this tool. However, it does not explicitly state when NOT to use it or compare it to siblings like 'search_within' or 'subscribe'. More explicit exclusion guidelines would improve this dimension.

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