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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description focuses on what annotations can't say: results include only recorded items, plus expected bills not yet received, and are measured against the latest statement cash. 'Nothing unrecorded is assumed' is a genuinely valuable modeling caveat. Missing only notes on result limits or empty-set 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?

A single compact sentence that leads with the object of the query and then qualifies it with the cash comparison and the recorded-only caveat. The parenthetical enumeration is dense but each item adds discriminating information; nothing is padding.

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 two-optional-parameter read tool with full schema coverage, the definition conveys what is included, how it is ordered, what it is compared against, and the key assumption. The absence of an output schema leaves the exact result shape (columns, totals, pagination) unexplained, which is the remaining 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?

Schema coverage is 100%, with both `days` and `as_of` fully documented including defaults and ISO format. The description's 'next weeks' and 'from which day' only loosely echo those parameters without adding syntax or edge-case meaning, so the baseline 3 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 enumerates exactly what the tool returns — bills, card payments, loan payments, subscriptions, expected-but-unreceived bills — sorted by date and paired with statement cash. That is a concrete, specific scope an agent can act on. It loses a point only because it never contrasts itself with close siblings like purch_payables or purch_card_dues.

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?

Usage is only implied: the cash-versus-dues framing suggests a near-term liquidity check, but there is no explicit statement of when to call this rather than purch_payables, purch_card_dues, or purch_subscriptions. No exclusions or prerequisites are given, so the agent must infer the routing.

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