Budget Set Budget Group Rollover

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

Annotations already indicate readOnlyHint=false and idempotentHint=false, and the description adds 'This may create or update Monarch data,' which clarifies the side-effect profile. However, it does not disclose what happens to existing rollover settings, whether changes are reversible, or any permission requirements.

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 core purpose is front-loaded, and the second sentence adds a relevant side-effect warning without unnecessary detail.

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 seven parameters, no output schema, and openWorldHint=true, the description is too thin. It does not explain what rollover configuration involves, how the parameters interact, what the response looks like, or which preconditions or side effects should be expected. An agent would likely need external knowledge or trial-and-error to invoke this 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?

Schema description coverage is only 29%, and the description adds no parameter-level meaning. Required parameters like category_group_id and enabled are left to name inference, and optional fields such as start_month, rollover_type, and starting_balance are not explained. The description does not compensate for the schema's sparse documentation.

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 clear verb and resource: 'Set budget group rollover.' This distinguishes it from sibling tools like budget_set_budget_category_rollover by the 'group' scope, though it does not explain what rollover means or how it differs functionally from related budget tools.

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?

No guidance is given about when to use this tool versus alternatives such as budget_set_budget_category_rollover, budget_set_flex_rollover_settings, or budget_reset_budget_rollover. The usage context is only implied by the tool name and sibling list, not stated in the description.

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