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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the response includes totals, recent entries, recurring items, and unlogged-spend notes, giving useful content context, but it does not discuss pagination, limits, or whether 'recent entries' is truncated.

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?

One compact fragment with no filler; every element maps to a returned data category. It could be slightly more structured (e.g., a full sentence or explicit 'returns'), but there is no wasted text.

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 is the only place that tells the agent what comes back, and it does list the main data categories. However, it omits detail about the shape of 'recent entries', any limits, and how this relates to list_budget_entries, leaving some ambiguity for a read tool.

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% and the single optional project_id parameter is fully documented in the schema. The description does not mention project_id at all, so the baseline 3 applies – the schema does the work.

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?

Names the resource and enumerates the data it returns (total, spent, recent entries, recurring items, unlogged-spend notes), which is more specific than a bare 'get budget'. However, it is a noun fragment with no verb and does not explicitly distinguish itself from the sibling list_budget_entries, leaving the agent to infer that this is a summary rather than a list.

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?

Provides no when-to-use guidance, no exclusions, and does not mention the sibling list_budget_entries, which also deals with budget entries. The agent must infer from the name and the enumerated fields that this is the summary view.

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