Budget Get Budget Settings

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds no behavioral context beyond saying 'Get'. It doesn't mention what output shape to expect, whether any hidden side effects are absent, or any rate/authorization considerations. No contradiction, but no value added.

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?

Single sentence 'Get budget settings.' has no filler and is direct; front-loaded and easy to parse.

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?

Despite rich schema and annotations, no output schema exists, and the description doesn't clarify what budget settings are returned (e.g., currency/date formats) nor how this differs from budget_get_flex_rollover_settings. For a tool with several budget siblings, this is insufficient context.

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 100%, with clear descriptions for fields and output_mode, including enum meanings. The description itself adds no parameter semantics, so baseline 3 applies.

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 ('Get') and resource ('budget settings'), so an agent can tell it is a read operation. However, it doesn't expand on what counts as 'budget settings' or distinguish it from sibling budget_get_flex_rollover_settings, leaving some ambiguity.

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 on when to use this tool versus alternatives; there is no mention of conditions or exclusions. The sibling set includes budget_get_flex_rollover_settings and budget_get_budget, so the agent must infer selection from the name alone.

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