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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: no background monitoring, no alerts, and that missing balances, dates or exchange rates prevent a confident estimate. It stops short of describing staleness or refresh timing, so it is strong but not exhaustive.

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?

Four short sentences, front-loaded with what the tool returns and followed by routing and limitations. Each sentence carries weight; only the 'it does not monitor in the background or send alerts' clause is mildly redundant with the readOnly annotation.

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 an output schema present, the description need not explain return values, and it covers purpose, routing, and data-quality caveats. The one gap is the absence of any guidance on the household_id parameter, which is the only input.

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 description coverage is 0% for the single household_id parameter, and the description never mentions it or explains what happens when it is omitted (it is optional with a null default). The one parameter that governs which household's data is returned is left entirely to the schema's type information.

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 verb and resource: returns today's raw cash-safety signal plus its assumptions, computed on demand, figures only. It explicitly distinguishes itself from the sibling get_household_answers by scope (detail vs. overview/budget question), so an agent can route without opening the schema.

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?

Gives an explicit when-to-use ('when the user asks for this detail') and names the alternative for the adjacent case ('a budget question or an overview is answered by get_household_answers'). Both the selecting condition and the alternative tool are stated, leaving nothing to inference.

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