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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that every claim has published inclusion criteria and sources, which adds some data-quality context, but it omits basic operational traits such as whether the tool is read-only, paginated, or returns a static dataset.

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 single, front-loaded sentence that efficiently conveys the resource's scope and key attributes without any filler or repetition. Every part of the sentence earns its place.

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 simple, zero-parameter list tool with no annotations or output schema, the description adequately explains what the records contain and their sourcing. It could be slightly more explicit about returning a list of records, but the tool name "list_incidents" compensates for that minor 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?

The tool has zero parameters, so the baseline score is 4. The description does not discuss parameters (there are none), and no additional param semantics are needed.

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 identifies the resource as a record of frontier AI control incidents, listing specific incident types (containment escapes, unsanctioned live-system actions, etc.) and distinguishing it from sibling tools that cover trackers, stats, watch, and index. However, it lacks an explicit action verb like 'list' or 'retrieve' and relies on the tool name to convey that it returns a list.

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 provides no guidance on when or why to use this tool versus alternatives. It does not mention any conditions, prerequisites, or exclusions, leaving the agent with no usage context beyond the content itself.

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