Household summary

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

With readOnlyHint=true already covering the safety profile, the description adds useful behavioral context: output is 'spoken-ready' and includes a check of whether the audit log is intact. It does not discuss authentication or rate limits, but it does not contradict the annotations and provides meaningful extra context beyond them.

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?

The description is two short sentences with no filler: the first states what the tool produces in specific terms, and the second confirms there are no required inputs. It is front-loaded and every word earns its 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?

For a zero-parameter, read-only summary with an output schema, the description fully covers what the tool reports and in what format. Nothing needed for an agent to select and invoke it correctly is missing.

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 has zero parameters and 100% schema coverage, so there is nothing for the description to explain semantically. 'Needs nothing' usefully reinforces that the tool requires no arguments, which is the only parameter-related information an agent needs.

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 names a specific verb ('Gives'), a specific resource ('spoken-ready overview'), and enumerates the exact content categories: due, overdue, waiting for approval, and audit-log integrity. This clearly differentiates it from the many sibling list/detail tools by framing it as an aggregate, voice-friendly summary.

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 intended use is reasonably clear: call this when a spoken-ready household overview is wanted. However, the description does not explicitly state when not to use it or route to more detailed siblings like list_pending_actions, get_audit_log, or get_budget_summary, so the usage guidance remains implied rather than explicit.

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