Budget Get Budget

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

Annotations already mark this as readOnly, idempotent, open world, and non-destructive. The description adds no behavioral context beyond that, such as whether the budget must pre-exist, how output_mode alters behavior, or what happens when no data is found. It does not contradict 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 extremely short but this is under-specification rather than effective conciseness. It front-loads nothing because it contains no useful information beyond the tool name. A minimal description can earn points, but only when the remaining substance is present in schema or annotations.

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?

There is no output schema and no return-shape description, so an agent cannot know what data to expect. The tool has one required parameter (month) whose format is not clarified, and no guidance distinguishes this from related budget tools. This description is not 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 schema describes the fields and output_mode parameters, but the required month parameter only has a title and type. The description provides no clarification of acceptable month formats or meaning. With 67% schema coverage and no parameter details in the description, the required parameter remains underdocumented.

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 "Get budget." is essentially a restatement of the tool name budget_get_budget, providing no additional detail about what 'budget' refers to. It does not distinguish this tool from closely related siblings such as budget_get_budget_category or budget_get_budget_settings.

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 offers no guidance on when to use this tool versus alternatives. There is no mention of the required month parameter, expected context such as retrieving a specific month's budget, or exclusions like budget category or settings retrieval.

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