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

Annotations already establish read-only, non-destructive, closed-world behavior, yet the description still adds substantial value: cross-page name matching semantics, ambiguity refusal (an error mode), inclusion of disabled groups, the extra accountAutoPauseRuleSets payload, and the crucial distinction that currentPeriodStart/End bound only the period and not the group's lifetime. This is behavior beyond what structured fields convey.

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?

Four sentences, front-loaded with the top-level purpose and the performance-data exclusion before mechanics. Every sentence carries information, though the reset-semantics sentence is dense and could be marginally tightened.

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 no output schema, the description does the work of noting that accountAutoPauseRuleSets is returned and framing currentPeriodStart/currentPeriodEnd, which is enough for an agent to interpret the result shape. It stops short of enumerating the full configuration payload, leaving some gaps about the response.

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% and already documents the name parameter's case/whitespace handling, so the baseline is 3. The description adds meaningful semantics beyond the schema: matching spans search pages and ambiguous names are refused, telling the agent the lookup can fail on duplicates.

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?

States a specific verb and resource ('Get configuration and settings for a budget group') and immediately distinguishes itself from performance tooling with '(NOT performance data)', which cleanly separates it from siblings like budget_group_performance and budget_group_performance stats. An agent can select it without opening the schema.

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 scopes usage by ruling out performance data and by describing matching behavior (full stored name, case/whitespace-insensitive, includes disabled groups, rejects ambiguous names). It does not name the alternative tool to use for performance data, so the routing hint is implicit rather than explicit.

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