Get Budget Health

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that it 'combines' multiple data sources and discloses an approximate cost of 4 API requests, which is relevant for rate-limit expectations. This adds value beyond annotations, though no auth or other behavioral details are mentioned.

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 moderately long but each sentence earns its place: core components, thresholds, usage guidance, and cost. Information is front-loaded with the snapshot description before interpretation details. Slightly verbose with the threshold list but still efficient.

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?

Given the tool's complexity and the presence of an output schema, the description covers what the tool computes, how to interpret thresholds, when to use it, and an approximate cost. Nothing critical is missing for an agent to invoke it correctly.

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 input schema already fully documents the single optional parameter 'budgetId' with 100% coverage. The description does not add any semantic detail about the parameter beyond what the schema provides, so the baseline of 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 states a specific verb ('get') and resource ('budget health snapshot'), enumerates the components (month data, balances, trailing-3-month income/spending summary) and indicators (savings rate, age of money, etc.), and distinguishes it from sibling tools like get_budget or get_month by framing it as an aggregated opening move.

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 states when to use: 'opening move of a monthly review or how-am-I-doing question', and advises to 'then drill into specific tools', implying alternatives without needing to name them. The threshold guidance also helps the agent interpret results, which is part of using the tool correctly.

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