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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds the key behavioral fact the annotations cannot: the exact membership rule of the returned set (status + date thresholds), which is the crux of a computed list tool with no parameters. It does not describe ordering or result limits.

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?

Two short sentences with no filler: the definition of 'due for follow-up' is front-loaded, and the usage phrase follows. Every clause 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?

With no parameters, no output schema, and annotations covering read-only safety, the description supplies what remains: what the result set contains and when to reach for it. Return field structure is unspecified, but that is a minor gap for a filtered-list tool.

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 takes zero parameters, so there is nothing for the description to clarify beyond the implicit filters, which it does in the criteria sentence. Baseline 4 applies for a no-parameter tool.

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 names the resource (quotes) and specifies the exact inclusion criteria for the derived list: past next_follow_up_date or sent >5 days ago. This distinguishes it from a generic find_quotes sibling, though the verb ('list/return') is implied rather than stated.

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 maps user phrasing directly to the tool with two trigger phrases ('quotes to chase', 'open quotes'), which is clear usage context. It stops short of naming an alternative tool or stating when not to use it (e.g., versus find_quotes for arbitrary querying).

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