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

Annotations already carry readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description nonetheless adds a meaningful clarification beyond them: 'sends nothing' reassures the agent that consulting a dunning queue never dispatches reminders, and the urgency ordering is extra behavioral context. Return shape and result-size limits are not covered.

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?

One compact sentence plus a short safety clause; the scope-defining content is front-loaded and every phrase (status list, sort order, read-only) contributes information.

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, read-only list tool with full annotation coverage and no output schema, the description supplies everything needed to decide to call it and what set it returns. Only the volume/shape of results is left unstated, which is a minor gap given the absence of an output schema.

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 and the schema is empty, so there is no parameter semantics to explain; baseline 4 applies. The description correctly implies no filtering or paging inputs exist.

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?

States a specific resource (the dunning queue / Mahnwesen), precisely enumerates its membership (overdue or reminder_1/2/3 outgoing invoices), and gives the ordering ('sorted by urgency'). The explicit 'outgoing' also separates it from the sibling fetchOverdueIncomingInvoices.

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 domain terms imply the situation in which to call it, but there is no explicit when-to-use statement, no exclusion, and no sibling named as the alternative for, e.g., incoming overdue invoices. Usage is inferable rather than stated.

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