Get Monthly Budget

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive hints. The description adds value by disclosing overspending flags, zeroes for inactive categories, and the absence of target data, going beyond annotations.

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 sentences, front-loaded with core purpose, then details on hidden categories and zeroes, then a note about no targets. Every sentence adds value; no redundancy.

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 3 parameters, no output schema, and moderate complexity, the description covers return values (income/budgeted/activity totals, per-category budget figures with overspending flags), behavior for hidden categories and zeroes, and what is excluded (target data). It is nearly complete but could specify top-level totals more explicitly.

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 parameter descriptions. The description adds context: month defaults to current month, budget_id defaults to last-used, include_hidden defaults to false for cleaner review. This enhances understanding beyond the schema.

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 clearly states 'Get a month overview with income/budgeted/activity totals and per-category budget figures', specifying the verb and resource. It distinguishes from sibling tools like list_budgets (list budgets) and get_targets (target data) by noting 'No target data'.

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 description provides context like 'Returns all visible categories by default' and 'set include_hidden=true to include hidden ones', and explicitly states 'No target data', implying use get_targets for that. However, it does not explicitly name alternatives or state when not to use this tool.

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