list_budgets

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

No annotations exist, so the description carries the full burden. 'Показать' implies a non-mutating read, and the description usefully discloses that the output aggregates the general and uncategorized budget. It says nothing about permissions, whether empty months return an empty set, or result ordering.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity comes partly at the cost of the parameter guidance noted above rather than pure economy.

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 one-parameter read tool with no output schema and no annotations, the description covers the purpose and the composition of the result but leaves the month format and response shape unstated. Adequate, but an agent must fall back to the regex to call it correctly.

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% for the single required parameter 'month'; the only hint is the schema's regex pattern, which an agent may not read as intent. The description's 'за месяц' merely restates the parameter name and gives no format (YYYY-MM), timezone, or current-month default.

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 states a specific verb and resource ('Показать бюджеты' — show budgets) scoped to a month, and clarifies the result includes the overall and uncategorized budget. That scope note helps distinguish it from the mutation siblings set_budget/delete_budget, though it never names them explicitly.

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?

Usage is only implied: 'за месяц' signals this is a monthly read, and the sibling set/delete_budget tools make the read-vs-write split inferable. There is no explicit when-to-use, no exclusion, and no mention of the alternative of reading a single category's budget.

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