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

No annotations exist, and the description carries the full behavioral burden. It states what items are included, why they matter, and defines the ordering ('Most serious first'), which is substantive behavioral context for an agent.

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?

A single front-loaded sentence communicates purpose, selection criteria, relevance, and ordering with zero redundancy.

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 parameterless list tool with no output schema, the description gives the agent enough to call it correctly and interpret results: what is returned and in what order. No critical operational detail is missing.

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 no parametersags, so the schema leaves nothing to document. The description adds semantic context about what the list contains, so the baseline of 4 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?

The description uses a specific verb ('List') plus a clearly scoped resource ('overdue or missing compliance items'), and sharpens it with relevance cues ('citable in OSHA inspection, injury investigation'). This distinguishes it well from sibling tools like get_requirements_due.

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 provides clear context by naming the selection criteria (overdue/missing) and the situation where this list matters (OSHA inspection, investigations). It doesn't explicitly contrast it with sibling tools, so the when-to-use guidance is good but not fully explicit.

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