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

With no annotations, the description must carry full behavioral disclosure. It states the tool lists overdue intervals and sorts by severity, which is useful. However, it does not mention permission requirements, return format, or what happens with no overdue items. It partially covers behavior.

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 sentence with a clear verb first and no filler. The em-dash clause adds important context, and 'Most serious first' is a concise ordering instruction.

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 zero-parameter list tool, the description conveys the domain (fire safety and health compliance), the filter (overdue), and the ordering. It falls short of describing the response fields, but given no output schema, this is a 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 schema defines zero parameters, and schema coverage is 100%. The description does not need to explain parameter semantics, so the baseline score 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 the verb 'List' with a specific resource 'overdue fire safety and health compliance intervals' and adds ordering 'Most serious first.' This clearly distinguishes it from siblings like get_services_due and search_services by emphasizing overdue and severity.

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 phrase 'the ones that create insurance and inspection exposure right now' provides clear context for when to use this tool—when there are immediate compliance risks. It implies urgency and filtering, though it does not explicitly mention alternatives or exclusions.

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