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

Beyond readOnlyHint/openWorldHint, the description discloses the real operational traits: $0.02 per event returned, an empty page being free, the requirement for a Quorumz API key as a Bearer header on this connection, and a 100-call/7-day free allowance. It also discloses result ordering and that quorum data is only present 'when one exists' — the kind of non-obvious detail that prevents misuse.

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?

Front-loaded with what alpha events are, then payload, then filters, then cost/auth. Three dense sentences with no filler, though the final sentence bundles pricing, empty-page behavior, keys, and free-tier limits into one long clause.

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 an output schema present, the field list is somewhat redundant, but cost, authentication, and paging expectations are all covered, which matters for a paid, keyed endpoint. The only gap is that alpha_kind and alpha_score are returned but their meaning or value range is never characterized.

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 baseline is 3, but the description adds genuine meaning by tying cost to the limit parameter ('costs $0.02 per event returned') and by framing cell/country as filters over the newest-first stream. It doesn't explain cursor mechanics beyond what the schema already says.

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 defines the resource concretely — 'stories flagged ahead of the wider press' — and states the ordering ('newest first') plus the data each event carries, so an agent knows exactly what comes back. It stops short of differentiating this from list_news or search_quorums, so the agent must infer whether alpha events or general news is the right feed.

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?

Filtering options (country, geohash cell) are stated, which implies when to use them, but there is no explicit guidance on when to choose this tool over list_news or the quorum siblings, and no stated exclusions. Usage is implied rather than directed.

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