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

With readOnlyHint, idempotentHint, and destructiveHint all false, the annotations provide no safety profile, so the description carries the burden of explaining side effects. It describes output categories but never explicitly states whether calling the tool mutates anything or only reports; it does add useful context by noting that fully-lettered invoices need a decision 'outside this server.'

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 one structured sentence with a front-loaded subject and a colon-delimited list of distinct output categories. Every clause carries information about the report's scope, and there is no filler or redundant repetition of the title.

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 that there is no output schema, the description does a good job enumerating the main return categories: escalated invoices, recommended letters, wait times, due-soon items, and invoices requiring external decisions. It omits exact threshold values, letter mappings, and empty-result behavior, but for a two-parameter report tool this is reasonably complete.

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 input schema already covers both parameters with 100% description coverage, giving a baseline of 3. The phrase 'what falls due in the next few days' loosely echoes within_days, but the description adds no parameter-level detail, formatting, or constraints beyond what the schema provides.

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 opening phrase 'The day's chase list' is vague on its own, but the colon-delimited enumeration names concrete resources: invoices crossing an escalation threshold, the letter to send and wait time, upcoming due dates, and fully-lettered invoices needing an external decision. This clearly distinguishes it from siblings like overdue_list and aging_summary in substance, even though no sibling is named.

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 day's chase list' implies a daily operational use case, and the description indirectly contrasts with sibling tools by describing a combined report. However, there is no explicit 'use when' guidance, no mention of when not to use it, and no named alternative such as overdue_list for the due-soon portion.

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