Budget Set Budget Group Variability

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

Annotations already signal this is a mutating operation (readOnlyHint=false, idempotentHint=false). The description adds that it 'may create or update Monarch data,' which gives a bit more specificity about upsert-like behavior, but it does not disclose side effects, reversibility, or what happens to existing values.

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 and front-loaded with the primary action in the first sentence. The second sentence about creating or updating is relevant and not redundant, though it adds limited behavioral depth. No unnecessary wording is present.

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?

The tool is relatively simple, but the description omits important context such as what 'variability' means, which budget timeframe is affected, and what the response contains. The schema covers the output-mode fields, and annotations cover the safety profile, but the description is barely sufficient for correct invocation.

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 required parameters category_group_id and variability have no schema descriptions, and the description does not explain them either. The enum values for variability are self-explanatory and the parameter names are somewhat obvious, but the description compensates for none of the missing required-parameter 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 specific verb and resource: 'Set budget group variability.' It is clear about what the tool does, though it does not explicitly distinguish itself from the closely named sibling budget_set_budget_category_variability beyond using 'group' instead of 'category.'

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 provided about when to use this tool versus alternatives such as budget_set_budget_category_variability or budget_set_budget_group_rollover. The description does not mention prerequisites, exclusions, or conditions that would help an agent choose this tool correctly.

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