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

With no annotations provided, the description carries the full burden and delivers rich disclosure: it explains the polling source (RIPEstat), the self-baselining mechanism, the event-type taxonomy with severity mapping, and return semantics including 'count is the full filtered set; events is bounded by limit, newest first.' This goes well beyond what structured fields provide.

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 dense but purposeful; every sentence contributes technical or behavioral context. It front-loads the core purpose, then moves through usage and field semantics, using a clean list for event types and no filler.

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 lookup with no output schema, the description fully equips the agent: it explains all event_type values, severity implications, `prev_origins`, pagination semantics, and the honest meaning of an empty `events` array. It even notes reserved event types for future monitor passes, leaving no critical interpretation gap.

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 meaningful semantics: it explains that `limit` bounds the `events` array while `count` remains the full filtered set, and that results are newest-first. It also clarifies `resource` as a watched CIDR or ASN, which reinforces but goes slightly beyond the schema.

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 a specific verb and resource: 'Returns the routing anomalies the bgp-monitor has observed against TunnelMind's BGP watchlist', immediately distinguishing it from sibling lookup and verification tools. It also grounds the tool in the 'witnessability layer's routing dimension', making its unique role clear.

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?

Explicitly instructs when to use: 'Use this to check whether a prefix or ASN you depend on... has shown a hijack-shaped routing event.' This is clear context, but it does not name sibling alternatives or state when not to use it, so it misses the explicit exclusion criterion for a 5.

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