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

Annotations already establish read-only safety, yet the description adds substantive behavior: results are paginated, both switched-on and switched-off groups are returned by default, and reading a switched-off group has no side effect of enabling it. It also clarifies how reset-type groups relate to currentPeriodStart/End versus endDate, which is real context beyond the 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?

The description is front-loaded with the core action and keeps to three dense sentences with no filler. The final reset-group explanation is slightly tangential to a listing operation but still earns its place by explaining returned period fields that have no output schema.

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 usefully explains key returned fields (currentPeriodStart, currentPeriodEnd, endDate) and confirms pagination, covering what an agent needs to interpret results. The absence of output field detail beyond period semantics is the only notable gap.

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%, so all five parameters (page, size, status, sort_by, sort_order) are fully documented in the schema, and the description's notes on status semantics largely restate the schema's 'Omit to include both'. Baseline 3 applies since the schema does the heavy lifting.

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?

Clear verb+resource ('Browse and list budget groups') with scope stated as paginated enumeration of both active and inactive groups. It does not explicitly distinguish itself from siblings like get_budget_group or budget_group_performance, but the list-vs-fetch difference is inferable from the wording.

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 status clause implies when to filter versus not, which gives some usage context. However, there is no explicit routing guidance such as 'use get_budget_group to fetch a single group' or 'use budget_group_performance for metrics', so the agent must infer the alternative.

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