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

The description discloses that setting mark_read:true flags events as read and alters future calls, which is a behavioral side effect. However, the annotation declares readOnlyHint=true, implying no state modification. This contradiction undermines transparency. The description adds useful context about the feed being persistent, but the contradiction is a critical issue.

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 relatively concise with three sentences covering purpose, output details, filtering, mark_read behavior, and alternative access. There is slight redundancy between 'Pull fired events' and 'Returns the most recent alerts', but overall it is well-structured and front-loaded.

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 tool with 5 optional parameters and no output schema, the description covers the main aspects: what is returned, filtering, mark_read effect, and polling suitability. It lacks details on ordering (beyond 'most recent'), pagination, or error cases, but it is largely 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 description coverage is 100%, so the baseline is 3. The description adds minimal extra meaning beyond schema: it explains that mark_read flags events read and unread_only returns null read_at. For type and since, it simply restates schema. No significant added value.

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 your subscription feed' and specifies it returns recent alerts. It mentions key fields (source, citation_uri, raw payload) and filters (type, since). However, it does not explicitly differentiate from sibling tools like 'list_subscriptions' or 'recent_changes', so it slightly misses sibling distinction.

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 notes that polling works fine and provides an alternative REST endpoint for scripts/dashboards, indicating when to use the tool vs. direct API access. It does not mention explicit when-not-to-use scenarios or compare to other tools, but it gives good contextual guidance.

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