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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine context: the payload is raw figures with no analysis, and it includes overdue and undated obligations plus the IDs needed downstream for simulation or payment.

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?

Three tight clauses front-loaded with the returned content, then usage, then the alternative. Every sentence earns its place with no filler.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers scope, content, and routing. It stops short of documenting the sole input parameter, a minor gap for an otherwise coherent definition.

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?

Only one optional household_id parameter exists and schema coverage is 0%, so the description would need to compensate. It mentions IDs generally but never explains household_id's role, format, or null/default behavior, leaving the parameter semantics unaddressed.

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 (known unpaid bills, including overdue and undated) and its nature (raw data with IDs, figures only no analysis). The scope is clear, though it identifies itself mostly by what it is not (no analysis) rather than a crisp verb+resource framing.

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?

Explicitly says to use it 'when the user asks for this detail' and routes budget/overview questions to get_household_answers. Names one alternative and the selecting condition, but does not address the other siblings (simulate_payment_change, mark_obligation_paid) it feeds IDs into.

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