ecosystem_repo_events

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

No annotations exist, so the description carries the full burden. It adds real value by naming the four event types and the writer tools behind each, plus noting that ecosystem_scan and ecosystem_repo_manual_status produce no events. However, it omits ordering, retention/limits, and what happens for a repo with no events.

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 purpose sentence is front-loaded and the follow-up detail about event provenance is genuinely informative rather than filler. Slightly verbose in the parenthetical tool lists but nothing is wasted.

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?

An output schema exists, so return-shape explanation is unnecessary, and the description covers provenance and which tools feed the log. An agent has what it needs to call and interpret this tool 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 description coverage is 100% with only two parameters, both documented in-schema (including default and max on limit). The description adds no semantics beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb and resource: 'Return event history for a single ecosystem repo.' An agent can tell this is a per-repo read, distinct from ecosystem_scan_history or event_list. It stops short of explicitly naming those siblings, so a 5 isn't warranted.

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?

Usage is implied (query events for one repo) and the description usefully maps which upstream tools generate which event types, which helps an agent interpret results. But it never states when to prefer this over ecosystem_scan_history, event_list, or ecosystem_index_diff_latest.

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