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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so safety is covered. The description adds value beyond them: sort order (oldest first), the derived fields returned (days overdue, total open), and an explicit negative capability — 'the system never sends anything' — which prevents the agent from assuming it triggers dunning.

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, front-loaded with the content of the result before the behavioral caveat. The color phrases ('the morning read', 'Chasing is the freelancer's act') are mildly decorative but do convey intent and scope of responsibility, so they largely earn their 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 output schema, the description carries the return-value burden and does so at a high level: sort order, per-item overdue age, and an aggregate open total. It stops short of naming exact fields, currency handling, or whether partially paid invoices are included, which would be needed for a full 5.

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 no parameters and the schema is an empty closed object, so there is nothing to disambiguate. Baseline 4 applies; the description correctly avoids inventing filtering arguments that do not 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 concrete verb-and-resource: 'issued, unpaid invoices oldest first, with days overdue and the total open.' An agent knows exactly what data comes back and in what order. It does not name a sibling it is distinct from (e.g. o2c_ar_aging or solo_reminders), so it stops short of a 5.

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?

'This is the morning read' implies a routine day-start check, which is real usage context. But there is no explicit when-not and no routing to alternatives like solo_reminders (for chasing actions) or o2c_ar_aging (for bucketed aging), leaving the agent to infer boundaries among many overlapping receivables tools.

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