Budget Set Budget Category Rollover

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

The description states 'This may create or update Monarch data,' which loosely reflects the openWorldHint and non-idempotent annotations, but it adds no meaningful behavioral context beyond those structured signals. It does not disclose whether existing rollover settings are overwritten, what side effects occur for budget calculations, or what data is affected. Since annotations already signal mutation and non-idempotency, the description carries minimal extra value.

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 short, but brevity is not the same as conciseness. The first sentence simply restates the tool name, and the second is a generic mutation warning that is already encoded in annotations. Neither sentence earns its place by adding useful information.

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 10 parameters, no output schema, and only 20% schema description coverage, this definition is far from complete. It lacks explanation of rollover behavior, the role of each parameter, expected input formats, and return values. The surrounding sibling list shows there are closely related rollover tools, but the description provides no context to choose among them.

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 20%, and the description does not compensate for the undocumented parameters. Required parameters like category_id and enabled are not explained, nor are optional ones such as frequency, rollover_type, target_amount, apply_to_future, and starting_balance. An agent cannot determine valid formats, expected date conventions, or how these parameters interact.

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 and resource: 'Set budget category rollover.' This distinguishes it from sibling tools like budget_set_budget_group_rollover through the 'category' qualifier, though it does not explain what rollover means or how it differs from reset_budget_rollover. It is clear enough for initial identification but lacks differentiation detail.

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?

There is no guidance about when to use this tool versus alternatives such as budget_set_budget_group_rollover, budget_set_flex_rollover_settings, or budget_reset_budget_rollover. The phrase 'This may create or update Monarch data' is a side-effect warning, not a usage condition. An agent has no basis for selecting this tool over its siblings.

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