budget_status

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully discloses the default month behavior and the inclusion of burn pace, which goes beyond the schema. However, it does not explicitly state that this is a read-only operation or describe behavior when no budget is set, leaving some ambiguity.

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 a single sentence with no filler. The core purpose is front-loaded, and the month format/default and burn-pace detail are presented efficiently. Every phrase earns its place.

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?

For a simple one-parameter read-style tool with an output schema, the description is nearly complete: it explains the input format, default behavior, and what the result covers. It does not explain what 'burn pace' entails or explicitly state that budget is required, but these are not necessary 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?

Schema description coverage is 0%, but the description fully compensates for the single parameter. It specifies the exact 'YYYY-MM' format and clarifies that omitting the month defaults to the current month, which the schema's null default does not convey.

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 identifies a budget-vs-actual comparison for a specific month, which clearly conveys the tool's purpose and scope. It includes the month format and burn-pace output, but lacks an explicit action verb and does not explicitly distinguish itself from siblings like summarize or query_expenses.

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 description gives clear context—use it for a monthly budget comparison with burn pace—but it does not state when to prefer this tool over alternatives such as summarize, set_budget, or query_expenses. There are no explicit exclusions or sibling routing cues.

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