list_facts

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

With no annotations provided, the description carries the full burden and does so richly. It discloses the ordering ('ordered by fact_id ascending — OLDEST analyzed first'), the pagination contract ('page through with since=<returned next_since> until next_since comes back null'), and the nuance that a single page is not the newest data. It also explains the meaning of advisory_group_key and group_severity.

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 a tight set of four sentences, each earning its place: purpose, ordering/pagination, alternative, and advisory-key semantics. It is front-loaded with the core purpose and avoids 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?

Given the absence of an output schema and annotations, the description covers the essential behavioral contract: pagination, ordering, alternative usage, filter options, and the meaning of advisory fields. This is sufficient for an agent to select and invoke the 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 coverage is 100%, so the baseline is 3. The description adds meaningful usage context beyond the schema: it clarifies that `since` is a cursor driven by the returned `next_since`, and it explains filter semantics like severity being group-maximum. This elevates the score to 4.

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: 'Incremental SYNC feed of release facts' for CNCF/cloud-native projects, and details the types of changes covered. It explicitly distinguishes itself from the get_release sibling for latest-release queries, satisfying the sibling-differentiation requirement.

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?

It clearly states the intended use case: 'Built for keeping a local copy up to date.' It also provides an explicit alternative: 'For "what is the latest release of X" or "recent releases of X", use get_release (omit version for the newest) instead.' This is a clear when-to-use and when-not-to-use directive.

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